Unable to change server properties in WIndows Deployment Server 2008: Access Denied
I've setup WIndows Deployment Server on a WIndows 2008 server. I'm logged in as an administrator of the server. However, I always get Access Denied when I attempt to change any of the WDS properties (for example: Changing PXE response to Reaspond to all client computers). My settings don't save when I click Apply.
Looking around online, one solution is to Delegate Control to the WDS for the OU you wish to put new workstations in. However, I do NOT want to put any workstations into an OU. I want to build workstations that are just part of a Workgroup (a tech will manually add them to the domain later). In addition, I do not have authority in AD to Delegate Control to the server anyway.
Is there anyway to get access to change properties without delegating control for an OU?
Looking around online, one solution is to Delegate Control to the WDS for the OU you wish to put new workstations in. However, I do NOT want to put any workstations into an OU. I want to build workstations that are just part of a Workgroup (a tech will manually add them to the domain later). In addition, I do not have authority in AD to Delegate Control to the server anyway.
Is there anyway to get access to change properties without delegating control for an OU?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No you must be domain admin of the domain you have the WDS server in. If you can, maybe you can create your own domain and put the wds server in that, but I believe you would need dns server and dhcp server to interact with.
Here is a link to a site that claims to be able to deploy offline. But I have not tested it so use at your own risk.
http://www.deployvista.com/Default.aspx?tabid=36&EntryID=129
Here is a link to a site that claims to be able to deploy offline. But I have not tested it so use at your own risk.
http://www.deployvista.com/Default.aspx?tabid=36&EntryID=129
You may try to make your WDS server leave the domain and join the workgroup. Your server could then become a "standalone server". The workgroup could have the same name as the domain.
Check this article
http://technet.microsoft.com/en-us/library/jj648426.aspx
it explains how to deploy WDS on a Standalone server.
Check this article
http://technet.microsoft.com/en-us/library/jj648426.aspx
it explains how to deploy WDS on a Standalone server.
ASKER
Appreciate the feedback. I was hoping for different option but looks like domain admin access is the only way. Thanks.
ASKER