Can not set Computername during Setup (OOBE Phase)

%3CLINGO-SUB%20id%3D%22lingo-sub-132846%22%20slang%3D%22en-US%22%3ECan%20not%20set%20Computername%20during%20Setup%20(OOBE%20Phase)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132846%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3EI%20ask%20myself%20why%20Microsoft%20has%20dropt%20in%20Win10%20the%20posiblity%20to%20set%20a%20computer%20name%20during%20Setup%20(OOBE-Phase).%20Is%20so%20dammend%20nervy%20to%20run%20to%20OOBE%20first%20(and%20dont%20Register%20in%20AD%20or%20even%20AzureAD%20b'c%20it%20can%5Et%20be%20change%26nbsp%3Beasy%20later%20then)%26nbsp%3Bthe%20rename%20computer%2C%20Reboot%20and%20start%20with%20registration%3C%2FP%3E%0A%3CP%3EThx%20for%20feedback%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132949%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Can%20not%20set%20Computername%20during%20Setup%20(OOBE%20Phase)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132949%22%20slang%3D%22en-US%22%3E%3CP%3EHere%20is%20some%20detail%20about%20the%20card%3A%20looks%20Like%20Windows%2010%20Ready%26nbsp%3Bbut%20it's%20not.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.hp.com%2Fro-en%2Fdocument%2Fc04560659%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EInfo%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERegards.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132927%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Can%20not%20set%20Computername%20during%20Setup%20(OOBE%20Phase)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132927%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20sorry%20Microsoft%20does%20not%20have%20a%20fix%20for%20that.%20Probably%20Windows%2010%20is%20not%20the%20best%20OS%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132913%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Can%20not%20set%20Computername%20during%20Setup%20(OOBE%20Phase)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132913%22%20slang%3D%22en-US%22%3E%3CP%3E..%20sorry%20this%20has%20nothing%20to%20du%20with%20my%20question%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132911%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20not%20set%20Computername%20during%20Setup%20(OOBE%20Phase)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132911%22%20slang%3D%22en-US%22%3E%3CP%3Esorry%20but%20if%20don't%20have%20WDS%20or%20any%20other%20deployment%20solution%3F%20And%20that's%20the%20scenario%20Microsoft%20is%20leading%20his%20users.%20just%20buy%20a%20computer%20and%20use%20Office%20365.%20If%20have%20only%20AzureAD%20no%20local%20servers%20that%20there%20is%20no%20choise%20to%20setup%20computer%20Name%20and%20you%20end%20up%20in%20chaose%20in%20AzureAD%20b'c%20all%20have%20such%20stupid%20names%20like%20DESKT-U63H65.%20And%20about%20%22don't%20burden%20end%20users%22.%20Sorry%20what%20is%20now%20all%20ask%20during%20OOBE%20is%20much%20more%20complicated%20and%20it%20will%20be%20no%20bigger%20burden%20to%20have%20a%20prefilled%20field%20with%20a%20default%20computer%20Name.%20But%20what%20Microsoft%20did%20is%20given%20SysAdmins%20a%20huge%20bigger%20burden%20to%20set%20comptuer%20account.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132900%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Can%20not%20set%20Computername%20during%20Setup%20(OOBE%20Phase)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132900%22%20slang%3D%22en-US%22%3E%3CP%3EWrong%20Tread%20but%20any%20answer%20for%20my%20question%20%3F%20Im%20experiencing%20with%26nbsp%3Bthe%20following%26nbsp%3B%26nbsp%3Bissues%20more%20than%20one%20year.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132890%22%20slang%3D%22en-US%22%3ERE%3A%20Can%20not%20set%20Computername%20during%20Setup%20(OOBE%20Phase)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132890%22%20slang%3D%22en-US%22%3EI%20have%20a%20rare%20HP%2FAMD%20R7%20240%204GB%20Model.%20Any%20KB%20Patch%20anyone%20have%20because%20after%20all%20insider%20build%20the%20AMD%20Radeon%20Driver%20Stopping%20working%20because%20switch%20back%20to%20Microsoft%20driver.%20(Graphics%20Card%20Model%3A%20782613-001%20FOR%20HP%20AMD%20R7%20240%20Badger2%20FH%204GB%20GDDR3)%20Thanks%20Advance.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132880%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20not%20set%20Computername%20during%20Setup%20(OOBE%20Phase)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132880%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20was%20removed%20during%20Windows%208%20to%20simplify%20the%20OOBE%20flow.%26nbsp%3B%20Since%20most%20organizations%20set%20the%20computer%20name%20via%20an%20unattend.xml%20(joining%20AD%20at%20the%20same%20time)%20we%20didn't%20want%20to%20burden%20end%20users%20who%20didn't%20understand%20why%20that%20was%20needed.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi,

I ask myself why Microsoft has dropt in Win10 the posiblity to set a computer name during Setup (OOBE-Phase). Is so dammend nervy to run to OOBE first (and dont Register in AD or even AzureAD b'c it can^t be change easy later then) the rename computer, Reboot and start with registration

Thx for feedback

7 Replies
Highlighted

This was removed during Windows 8 to simplify the OOBE flow.  Since most organizations set the computer name via an unattend.xml (joining AD at the same time) we didn't want to burden end users who didn't understand why that was needed.

Highlighted
I have a rare HP/AMD R7 240 4GB Model. Any KB Patch anyone have because after all insider build the AMD Radeon Driver Stopping working because switch back to Microsoft driver. (Graphics Card Model: 782613-001 FOR HP AMD R7 240 Badger2 FH 4GB GDDR3) Thanks Advance.
Highlighted

Wrong Tread but any answer for my question ? Im experiencing with the following  issues more than one year.

Highlighted

sorry but if don't have WDS or any other deployment solution? And that's the scenario Microsoft is leading his users. just buy a computer and use Office 365. If have only AzureAD no local servers that there is no choise to setup computer Name and you end up in chaose in AzureAD b'c all have such stupid names like DESKT-U63H65. And about "don't burden end users". Sorry what is now all ask during OOBE is much more complicated and it will be no bigger burden to have a prefilled field with a default computer Name. But what Microsoft did is given SysAdmins a huge bigger burden to set comptuer account.

Highlighted

.. sorry this has nothing to du with my question

Highlighted

I'm sorry Microsoft does not have a fix for that. Probably Windows 10 is not the best OS

Highlighted

Here is some detail about the card: looks Like Windows 10 Ready but it's not.

Info

 

Regards.