up vote 1 down vote favorite
share [g+] share [fb]

I've set up a WDS 2003 server for OS installation. (2003 because we need XP support) I also want to use this server to store Acronis images of already installed PCs. The newly installed PCs would be cloned and the images would be stored on this server for later. This server is the DC as well, no other DCs are connected to the network, the only purpose of this server is image deployment and storage in an isolated environment.

My issue is that I can't enable anonymous access to the DC. When I try to save the image from the PC to the server it always prompts me for credentials. I have to type in "anonymous". I'd like to find the way to avoid this prompt as many technicians will use the server. I've read through several posts, plus I've done everything I've seen in this post as well, but still no success!

Also, the newly installed computers do not join the domain, they join the workgroup "WORKGROUP". From these computers I'm unable to browse the shares on the domain. I have to type in the full UNC path, than I'm prompted for credentials and only than I'm able to brows the server.

Does anyone know how to overcome these issues? Thank you!

link|improve this question
1  
I don't know why you think you need 2003 for XP support. You can deploy XP just fine from WDS in 2008R2. – MDMarra Oct 7 '11 at 18:50
Does this need to be a DC? It sounds like you really don't need it as a DC. – Coding Gorilla Oct 7 '11 at 18:52
Why not just hardcode credentials for a service account in a net use command? Enabling anonymous access to any domain controller for any reason via any protocol is not a good thing. – Shane Madden Oct 7 '11 at 18:53
@MarkM: WDS does not support flat images like XP, you need to install it on a reference computer, clone it and deploy that image. We use it on all sorts of PCs, have tried to create a universal image but it's too much work... WDS Legacy mode is a simpler solution Coding Gorilla: We don't want to install a second server, but WDS requires a DC – sisko Oct 7 '11 at 19:17
1  
Excuse me for saying so, but wanting to set up anonymous access to the DC because "many technicians will use the server" is not a good reason for allowing anonymous access to the DC. I need access to a lot of systems in my duties as a sysadmin and do you know what I do? I provide the appropriate credentials when prompted for them. I do not allow anonymous or unauthenticated access just so that my job is easier. I'm all for improving operational efficiency, but security shouldn't suffer as a result. – joeqwerty Oct 7 '11 at 20:01
show 1 more comment
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.