Microsoft forefront not updating client

When creating a provisioning package with Windows Configuration Designer (WCD) to join a device to Azure AD you can specify applications to install during the provisioning wizard, however these applications must be a single file. It allows for repackaging without having to install the application on a reference machine and capture the differences into a MSI file like most repackaging solutions.These self-extracting files can be deployed during the provisioning of a device.

microsoft forefront not updating client-80microsoft forefront not updating client-61

One those where it does not work, Windows Update still says, "You received updates: Managed by your system administrator" Clients are all Windows 7 and the servers are 2008 R2 with SCCM 2012 on the one doing Endpoint Protection.

So I'm wondering if there is a way to check which server the clients are connecting to to pull their Windows Updates?

Note: If you’re looking for a more efficient way to include Office 365 Pro Plus CTR into your provisioning package, use the Office Install Toolkit, which will give you the ability to customize your office install and download the bulk of the installation files to reduce the amount of bandwidth your devices will use during provisioning.

Option 1 is easy, however option 2 is a better test since the provisioning process uses the system context.

The flag didn’t disappear within 😉 “mine own accepted time frame” so I started playing with my Lync Client and added a status message. So I then went to the user’s Lync Client and click on What happening field.

It was blank but when I pressed the down arrow I could the lines from OOO.

The registry key mentioned by jbsmith is the place to look for on the client itself. You can have multiple servers, and you can target some machines to one or the other with group policy, but you can't split the updates so that OS updates come from one and virus defs from another.

You can also find the info in %WINDIR%\That logfile is also the place to check why updates failed to install. Whether it's a standalone WSUS server, or a Configuration Manager Software Update Point (SUP), does not matter -- but the limit is one. Any computer that is pointed to that server will show up in that list.

Use option 1 first just to validate that the exe works.

But use option two to make sure it works in the system context.

######Update###### 02/09/2013 I have recently come across this issue again but the resolution was different.

Tags: , ,