Windows 10 Help
-
No becuse it's the same model for all the computer ..
-
You still need to Sysprep to create new SID and other security things.
-
They only time you shouldn't Sysprep is when you are using the same image for the same person on the same machine.
-
@Dashrender said in Windows 10 Help:
They only time you shouldn't Sysprep is when you are using the same image for the same person on the same machine.
Would that be the cause of this type of issue, though?
-
How do i fix without reforamting system
-
There is no way to a sysprep when creating an image using windows system image
-
@mroth911 said in Windows 10 Help:
There is no way to a sysprep when creating an image using windows system image
I've heard some folks will build their master image as a VM, and then sysprep that, and make an image of it. Then it can be restored to new VMs, or even new physical devices, like laptops, etc.
Build the new image, and get it the way you like it, with whatever software needs to be installed. Then right before you sysprep the machine, take a snapshot of it.
Then do the sysprep, and take your image. You can then use that new image to work on Laptops, or Desktops, etc.
-
Unfortunately, that's not much help for the situation you are in now.
-
I dont know the solution to the current problem, sorry.
-
:slight_frown:
-
You can sysprep an installed system.
Sysprep /generalize /shutdown /oobeThis will sysprep the already installed system and Out of Box Experience the desktop. So remove it from the domain first.
Then when you go to login, you'll have to activate the desktop etc.
As for if this will fix the desktop issue as described I would think the issue is GPO related and not image related.
-
It could be a group Policy issue... Here's a thread from SW with a couple of GPO things you can check...
-
Let me also throw in.. that I am running server 2008 on my dc.
-
@mroth911 said in Windows 10 Help:
Let me also throw in.. that I am running server 2008 on my dc.
Not that shouldn't matter.
