I am in the process of moving from WDS to MDT. I will be installing MDT alongside WDS on the same box. The concept I am not grasping is at what point in this process will clients pxe boot to the MDT service instead of the already established WDS instance?
Thanks in advance!
I had a bizarre issue today where NT SERVICE\MSSQLSERVER was being denied login as a service on a domain joined computer. I also noticed group policy was not being applied via gpupdate /force. I disconnected the computer from the domain, deleted the AD Object, re-created the AD Object, and re-joined the domain. The computer pulled policy successfully, and SQL Express worked. I know the GPO's don't have anything to do with it because I scoured through them to see if there was a policy allowing the virtual account login as a service and there was nothing of the sort. There are only three GPOs being applied now and they are not related. I'm struggling to make sense how this fixed the SQL problem. The only thing that would make sense, even though the SQL instance is local, the computer still needed a kerberos token to login as the service. When I rejoined the domain, it fixed the connection to the DC allowing authentication. Does that make sense?
Thanks folks.
DataTansferService.log:
Successfully queued event on HTTP/HTTPS failure for server 'ADB-ITS-02.ad.mydomain.com'.
Error sending DAV request. HTTP code 0, status ''
Download timeout has met. DTS job {95D7ABBA-59BD-46B1-BD33-6C1661A8FEDF} will quit.
GetDirectoryList_HTTP('https://ADB-ITS-02.ad.mydomain.com:443/CCMTOKENAUTH_SMS_DP_SMSPKG$/Content_cb286a91-80a3-41fd-8a61-81ca0a50fdd5.1') failed with code 0x800705b4.
Error retrieving manifest (0x800705b4).
I am trying to get our sccm clients installed properly on our machines. It was working a few weeks ago but recently noticed that clients have not been installing properly. The CCM client is installed on the machines but only two evaluation cycle actions are present and we get errors in our ccm.log (posted below). I turned off both the server firewall and the client firewall but it made no difference.
Below is a shot of what happens in the log when we push the ccm client to a machine.
