Of course the best method is still to build a golden image, sysprep it (with the shutdown option), then create an image file from the powered off base station. And I've seen other shops use it on as many as 100 workstations after imaging and they never had any problems. I've only used it after imaging in a couple rare instances, but never had any problems. You get the same workflow in Docker Desktop and the. I wonder why this is officially unsupported? Has anyone run into any production issues with it? Simplify code to cloud application development by closely integrating with Azure Container Instances (ACI). For example if you cloned or performed a Physical to Virtual(P2V) of a computer but want to leave the source computer running instead of decommissioning it." "Microsoft does not support the use of Sysprep for the following scenarios To run sysprep after imaging or cloning production computer for the purpose of changing the SID and computername to join the domain and make the computer unique. In their Unsupported Sysprep scenarios, Microsoft states: Thanks for your post about using sysprep to change SIDs after imaging.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |