Need To Update Existing Image - Missing Some Pieces
-
You can try to deploy an image. Do not let the computer boot, boot it with a usb key (live cd), and backup the setupcomplete (c:\windows\setup\scripts) and the unattend (c:\windows\panther). These files are probably delete during first starts thats why you have to use a usb key or live cd.
-
@george1421 said in Need To Update Existing Image - Missing Some Pieces:
This question is a bit outside the scope of fog. Its more related to windows imaging requirements.
I’m not sure about the Win10unattend file, there should be a unattend.xml file that should go into c:\windows\panther. Here is an article about creating a Win10 reference image that may help: https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/create-a-windows-10-reference-image
The setupcomplete.cmd file is often created by the imaging tech during golden (reference) image creation. This script is run automatically after OOBE finishes and just before the initial windows logon prompt is displayed. You can read more about the setupcomplete.cmd file here: https://technet.microsoft.com/en-us/library/cc766314(v=ws.10).aspx
The link for creating a Win10 reference image is all about making one in an MDT build lab. Do I really need to go through all those steps to do this?
Honestly FOG seems a lot more complicated then what GHOST use to be. Build the image, sysprep it, boot from bootable drive and GHOST the image to a server. This seems really complicated. -
@dpotesta50 said in Need To Update Existing Image - Missing Some Pieces:
Honestly FOG seems a lot more complicated then what GHOST use to be. Build the image, sysprep it, boot from bootable drive and GHOST the image to a server. This seems really complicated.
Understand this is not FOG requiring anything. FOG is only an imaging too. Its MS Windows requiring a new way to do things to create an imaging capable for clongin. Once your reference image is created properly FOG will clone it no problem (actually if you create your master image improperly FOG will clone that too, it doesn’t care it only pushes bits around). Reference image creation and image deployment are two separate functions. You will have the same if you use other deployment tools.
-
@george1421 said in Need To Update Existing Image - Missing Some Pieces:
@dpotesta50 said in Need To Update Existing Image - Missing Some Pieces:
Honestly FOG seems a lot more complicated then what GHOST use to be. Build the image, sysprep it, boot from bootable drive and GHOST the image to a server. This seems really complicated.
Understand this is not FOG requiring anything. FOG is only an imaging too. Its MS Windows requiring a new way to do things to create an imaging capable for clongin. Once your reference image is created properly FOG will clone it no problem (actually if you create your master image improperly FOG will clone that too, it doesn’t care it only pushes bits around). Reference image creation and image deployment are two separate functions. You will have the same if you use other deployment tools.
So there’s no way around it, i need to create the MDT environment to create the 10 image?
-
@george1421 said in Need To Update Existing Image - Missing Some Pieces:
@dpotesta50 said in Need To Update Existing Image - Missing Some Pieces:
Honestly FOG seems a lot more complicated then what GHOST use to be. Build the image, sysprep it, boot from bootable drive and GHOST the image to a server. This seems really complicated.
Understand this is not FOG requiring anything. FOG is only an imaging too. Its MS Windows requiring a new way to do things to create an imaging capable for clongin. Once your reference image is created properly FOG will clone it no problem (actually if you create your master image improperly FOG will clone that too, it doesn’t care it only pushes bits around). Reference image creation and image deployment are two separate functions. You will have the same if you use other deployment tools.
This is a line in the Windows 10 deployment link you gave me. “With Windows 10, there is no hard requirement to create reference images”
I know for a fact the previous tech didn’t create this four machine environment as outlined in those instructions. There must be an easier way. -
@dpotesta50 Lets make sure we understand your end goal here. The link provided was to provide additional information about the unattend.xml file and the setupcomplete.cmd files from your original post. These are used when you create a reference image.
So are you trying to maintain and existing image or are you trying to create a new win10 image from scratch.
For windows imaging creating from scratch you can go the MDT route or you can take and setup a computer using the DVD, place the computer in Audit mode and then customize it as much as win10 will allow you. You don’t need MDT, you can always go the Audit mode route.
-
@george1421 said in Need To Update Existing Image - Missing Some Pieces:
@dpotesta50 Lets make sure we understand your end goal here. The link provided was to provide additional information about the unattend.xml file and the setupcomplete.cmd files from your original post. These are used when you create a reference image.
So are you trying to maintain and existing image or are you trying to create a new win10 image from scratch.
For windows imaging creating from scratch you can go the MDT route or you can take and setup a computer using the DVD, place the computer in Audit mode and then customize it as much as win10 will allow you. You don’t need MDT, you can always go the Audit mode route.
Yeah my apologies for not being clearer since my original post. I myself thought we were just updating an existing image but my boss decided to go the new image route instead. My fault for not stating that.
So yeah, fresh Windows 10 image. -
@dpotesta50 said in Need To Update Existing Image - Missing Some Pieces:
So yeah, fresh Windows 10 image.
My intent isn’t to seem snarky, but point you in the right direction. This isn’t a FOG problem, period. You need to understand the requirements of WIn10 image creation before FOG is an issue. You need to get a solid master image before you even talk about a deployment tool (any tool).
You have two basic paths you can choose from (I just randomly pulled this link from google)
- Audit mode: https://www.tenforums.com/tutorials/3020-customize-windows-10-image-audit-mode-sysprep.html
- MDT: https://deploymentresearch.com/Research/Post/540/Building-a-Windows-10-v1607-reference-image-using-MDT-2013-Update-2
Each has their own advantages and disadvantages. At my company we use the MDT route because we need to have a consistent reference image build because we update our golden image once a quarter with the latest updates. Once we verify the build process (task sequences) we don’t have to verify them each time we update the golden image. Having to do this by hand (using audit mode) would be very time consuming each quarter as well as verifying the system is correct each quarter. By the time we were ready to roll out the Q3 updated image it would be time to start working on Q4’s image.
-
@george1421 said in Need To Update Existing Image - Missing Some Pieces:
@dpotesta50 said in Need To Update Existing Image - Missing Some Pieces:
So yeah, fresh Windows 10 image.
My intent isn’t to seem snarky, but point you in the right direction. This isn’t a FOG problem, period. You need to understand the requirements of WIn10 image creation before FOG is an issue. You need to get a solid master image before you even talk about a deployment tool (any tool).
You have two basic paths you can choose from (I just randomly pulled this link from google)
- Audit mode: https://www.tenforums.com/tutorials/3020-customize-windows-10-image-audit-mode-sysprep.html
- MDT: https://deploymentresearch.com/Research/Post/540/Building-a-Windows-10-v1607-reference-image-using-MDT-2013-Update-2
Each has their own advantages and disadvantages. At my company we use the MDT route because we need to have a consistent reference image build because we update our golden image once a quarter with the latest updates. Once we verify the build process (task sequences) we don’t have to verify them each time we update the golden image. Having to do this by hand (using audit mode) would be very time consuming each quarter as well as verifying the system is correct each quarter. By the time we were ready to roll out the Q3 updated image it would be time to start working on Q4’s image.
Didn’t think you were snarky at all my friend. I appreciate the feedback. My fault for not clarifying my goals here.
Are the unattended files originally mentioned still needed? -
@dpotesta50 (snarky: I did amend my original post to reduce the snark level).
The unattend.xml and setupcomplete.cmd files are something created by your previous admin to tweak your windows 10 build post image deployment with company/site specific settings. You may want to review these files to understand why he felt the need to do this. I can tell you its common practice to use the unattend.xml and setupcomplete.cmd files. So the short answer is yes you may need them.
If you don’t have them, and your previous admin used them, I can tell you how to collect them (assuming they are in your master image today). Take a computer and deploy your standard image to it, when FOG is done, power off the computer. Take the hard drive out and add it as a second drive temporarily in another computer. This will give you access to the media to collect these files.
