Using Client Push Installation on UNTRUSTED FOREST systems with ConfigMgr 2012

Last week my post was about using the Client Push Installation on WORKGROUP systems and this week my post will be a sort of follow-up on that. This week my post will be about using the Client Push Installation on UNTRUSTED FOREST systems. The method of last week will also work on UNTRUSTED FOREST systems, but the nice thing about ConfigMgr 2012 is that there are now better options for UNTRUSTED FOREST systems! The systems and domain(s) of the UNTRUSTED FOREST can be discovered AND to make it even better, it is even possible to write information to the Active Directory! Prerequisites Before it is possible to use the Client Push Installation on UNTRUSTED FOREST systems, there are a few things to keep in mind. …

Read moreUsing Client Push Installation on UNTRUSTED FOREST systems with ConfigMgr 2012

Using Client Push Installation on WORKGROUP systems with ConfigMgr 2012

This week my post will be about using the Client Push Installation on WORKGROUP systems. We all know that a manual installation will work on WORKGROUP systems, but wouldn’t it be easier to just use the Client Push Installation? In my opinion the answer would be, YES! And as long as the WORKGROUP systems are configured the same, the configuration is actually quite easy. Prerequisites Before it is possible to use the Client Push Installation on WORKGROUP systems, there are a few things to keep in mind. The following points are a prerequisite and are not further explained in this post: The FQDN of the Management Point system can be resolved on the WORKGROUP system. The Network Discovery is enabled to find the WORKGROUP systems. …

Read moreUsing Client Push Installation on WORKGROUP systems with ConfigMgr 2012

ConfigMgr 2007, Client Push Installation – The server-side story

Sometimes its good to freshen-up some “hidden” knowledge. Its somewhere in your head, but it just needs to be freshened. One of these things is the Client Push Installation. In this post I will try to tell the story of the server side. Prerequisites for Client Push Installation To be able to do a successful Client Push Installation, the following prerequisites need to be met: There must be a Client Push Installation –account defined in the Accounts tab of the Client Push Installation Properties. The Client Push Installation –account must be a member of the local Administrators group on the targeted computer. The targeted computer must have been discovered a ConfigMgr discovery method. The targeted computer must have an ADMIN$ share. The targeted computer must …

Read moreConfigMgr 2007, Client Push Installation – The server-side story

ConfigMgr 2007, Client Push Installation and (a) Firewall(s)

One of the most common problems with Client Push Installation is (are) the (Windows) Firewall(s). As I had some questions about this (again) lately, I will post here all the open ports/ firewall exceptions needed for a Client Push Installation. Exceptions for the Windows Firewall To be able to do a Client Push Installation you need the following exceptions in the Windows Firewall: File and Printer Sharing Windows Management Instrumentation (WMI) TCP Port 80 (for HTTP from the client computer to a MP (Mixed Mode)) TCP Port 443 (for HTTPS from the client computer to a MP (Native Mode)) Specific ports for other Firewalls To be able to do a Client Push Installation you need to open the following ports in the Firewall: Description UDP …

Read moreConfigMgr 2007, Client Push Installation and (a) Firewall(s)