Forum Discussion
Query on Sysperp Windows 2016 with RDS role
I attempted to sysperp a Windows Server 2016 server configured as Remote Desktop Server (RDS).
Hosted on Hyper-v . I used sysprep to generalize the server in order to assign a new name, id and so on.
Microsoft documentation says that it is possible to use sysperp to generalize an RDS server.
After restarting the guest I see that it has been generalized by sysprep.
RDS setting, however, are not generalized and the guest maintains its original settings (before sysprep old server setting).
So, the cloned VM is unusable.
Any steps to follow to sysprep RDS server.
3 Replies
- Did you manage to fix your issue by following the steps above?
Was this enough information for you?
- The server that you want to sysprep and use that as a template for new RDS servers should not be joined to a deployment prior to sysprep, read an other discussion about that and the answer there was:
To remove a RDSH server you would follow the below general pattern:
Make sure all users are logged off, any user data in local profiles or other folders is backed up, etc.
Remove RDSH server from the collection via Server Manager -- RDS -- Collections -- <collection> -- Host Servers -- Tasks -- Remove RD Session Host servers
Remove RDSH server from the deployment via Server Manager -- RDS -- Overview -- Deployment Overview -- right-click on the RD Session Host icon and choose Remove RD Session Host servers
Once you complete the above you can proceed with sysprepping, cloning it, adding new servers to the domain, adding to deployment, adding to collection, testing, etc.
https://social.technet.microsoft.com/Forums/Azure/en-US/ee49fe32-c8e5-42c0-bc9f-16faa9f5b283/cloning-rds-host-servers?forum=winserverTS
