Thursday, June 07, 2012 2:11 AM
So I have been working with MDT 2012 and have successfully imaged and deployed several images without much hassle (once I was able to get the images the actually capture). Today I went to set-up one of these machines. For whatever reason, the particular machine could not access a particular server (it was giving errors account not authorized or something like that) but could access any other server. Logging onto the machine as domain admin did not work, nor did any kind of browse (I was able to ping it so i know the server was there and the user could log onto a different machine and access the server). I figured out its the image because I tried the image on a different machine and got the same result and then used a generic Windows DVD to install on the first machine and I was able to successfully access that server. I plan to rebuild the image tomorrow and check again.
My question is this-
what could have caused this? The only two things I can think of are some kind of driver issue, or something that went partially wrong with the sysprep that while allowed sysprep to succeed, did something strange.
Any ideas or theories are welcome
Thursday, June 07, 2012 9:30 AM
What is the exact message do you get? Are you trying to access a domain controller?
You could try to disjoin and rejoin the domain to make sure that the sercure channel is re-established.
Also - A good start would be to check Netlogon etc errors in the even viewer - Next, a netmon network trace can help in determining where the issue lies...
Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"
Thursday, June 07, 2012 3:24 PM
Here is the exact error message. The server name i have covered (which was simply a file server).
The server is a Windows 2000 Server and the desktop is Win 7 Pro x64
Tuesday, June 12, 2012 8:45 PM
so i just did a brand new capture and got the same result.
I will mention that the first time i tried to capture it complained about invalid credentials but when i started the process again, it seemed to work fine. I then tried to browse to that same location and got the same error.
Is there any kind of specific log I can look at?
Thursday, June 14, 2012 8:05 PM
- Marked As Answer by dkurz8814 Thursday, June 14, 2012 8:19 PM
Thursday, June 14, 2012 8:20 PM
Thank You Mreid.ceci-
This combined with another post else does answer my question.