Dear community
I'm experiencing a very strange issue.
We've got a Windows Server 2012 Standard acting as the WDS/MDT server. We use the most recent MDT 2012 Update 1. We've got an Intel DQ77MK computer as our test object. We are trying to deploy a Windows 7 image (directly imported from the ISO source) using the Lite Touch Installation.
The deployment seems to work except: We keep getting an error message "invalid credentials" everytime when the client gets restarted. I've inserted the IP address of the MDT server in the BootStrap.ini file. I can connect to the deployment share with the credentials I've typed in the BootStrap.ini file, so this must be working.
The funny part is: When I click on the retry button in this window, then the client continues with the next deployment steps.
The deployment continues and we always have to click on the retry button until the client reaches the end of the deployment. Then we'll face a lot of warnings because of these "disconnects".
You'll laugh at this: Someone told me that this must be a bug with MDT 2012 Update 1. The client's gigabit network interface seems to be "too fast", so the client's unable to connect to the deployment share before the deployment wizard gets started.
So I went ahead and limited the client's network interface down to 100 Mbps. Guess what: The "invalid credentials" error message didn't appear anymore! I also noticed that exactly at that moment when the error message pops out, there's a yellow triangle in the notification area. Seconds later it turns back into the icon it should be: Internet access.
I also tried to disable the IPv6 components as I thought it might be that, but it didn't work as well.
Did anyone experience this issue as well? How did you resolve it? Can I put in a simple wait command in one of the MDT scripts so the client waits 5 seconds before the deployment wizard pops out?
Thanks in advance!
Kind regards
Makorus
I'm experiencing a very strange issue.
We've got a Windows Server 2012 Standard acting as the WDS/MDT server. We use the most recent MDT 2012 Update 1. We've got an Intel DQ77MK computer as our test object. We are trying to deploy a Windows 7 image (directly imported from the ISO source) using the Lite Touch Installation.
The deployment seems to work except: We keep getting an error message "invalid credentials" everytime when the client gets restarted. I've inserted the IP address of the MDT server in the BootStrap.ini file. I can connect to the deployment share with the credentials I've typed in the BootStrap.ini file, so this must be working.
The funny part is: When I click on the retry button in this window, then the client continues with the next deployment steps.
The deployment continues and we always have to click on the retry button until the client reaches the end of the deployment. Then we'll face a lot of warnings because of these "disconnects".
You'll laugh at this: Someone told me that this must be a bug with MDT 2012 Update 1. The client's gigabit network interface seems to be "too fast", so the client's unable to connect to the deployment share before the deployment wizard gets started.
So I went ahead and limited the client's network interface down to 100 Mbps. Guess what: The "invalid credentials" error message didn't appear anymore! I also noticed that exactly at that moment when the error message pops out, there's a yellow triangle in the notification area. Seconds later it turns back into the icon it should be: Internet access.
I also tried to disable the IPv6 components as I thought it might be that, but it didn't work as well.
Did anyone experience this issue as well? How did you resolve it? Can I put in a simple wait command in one of the MDT scripts so the client waits 5 seconds before the deployment wizard pops out?
Thanks in advance!
Kind regards
Makorus