NobleComputing

If I take a machine from the office to home, the Configuration Manager does show Internet. We have a management point on the DMZ that the machine connects to get a list of updates. It looks like the workstation is making communication with that server based on the logs. What is not happening is the actual successful download of the patches and the installation of them. I read that the internet client should go to Microsoft updates first and then to a dp? We do not have a dp setup for the internet clients, as we want them to only download from the Microsoft, yet the packets I capture only point to the management point on the dmz. Any direction would be appreciated on getting these machines to download from windows update!

There has to be a simple answer to this and I am missing it. Here is what I want to run: MsiExec.exe /X{89F4137D-6C26-4A84-BDB8-2E5A4BB71E00} /qn Really all I need to do is run this command on a remote machine. Is there actually any files in the package? I would think no. Correct me if I am wrong. If it does not contain any files, how do I run the above command on the remote machine? Please advise... Do I have to create a file something.bat and place this command in it? If so, when I the bat file is kicked off, does it execute from the ccmcache folder, the temp directory .. or somewhere else?

The writing of the Bitlocker key to AD has been working flawlessly... until we started to receiving machines with SSD drives in them. The task sequence works flawlessly with no errors. The problem is the bitocker recovery tab within AD is empty. I can run the manual way (https://blogs.technet.microsoft.com/askcore/2010/04/06/how-to-backup-recovery-information-in-ad-after-bitlocker-is-turned-on-in-windows-7/ ) and it will input the data in to ad, but I do not want to have to do this . The real strange thing is if I remove the machine from AD, and reimage it, the key properly registers itself within AD. Only on the second pass will it work?

The writing of the Bitlocker key to AD has been working flawlessly... until we started to receiving machines with SSD drives in them. The task sequence works flawlessly with no errors. The problem is the bitocker recovery tab within AD is empty. I can run the manual way (https://blogs.technet.microsoft.com/askcore/2010/04/06/how-to-backup-recovery-information-in-ad-after-bitlocker-is-turned-on-in-windows-7/ ) and it will input the data in to ad, but I do not want to have to do this . The real strange thing is if I remove the machine from AD, and reimage it, the key properly registers itself within AD. Only on the second pass will it work?

All I need to do is copy a file from \\server\sources$\software\bytepro\file.xml to the c:\program data\ directory on one of the client machines in a collection. I thought I could just create a task sequence that looks like this : I get an error