Hi Prajwal, Thanks for beautiful information you share, I have installed the sccm 2012 on base machine(Server 2008 r2) and have VM(Hyper v) machine as a client. I am able to access VM from base machine.I created one package and made it as available and is showing in client machine Software center(VM)and when i click on install it is downloading the content but after that it says waiting to install but when i do the same thing to base machine it is installing. I checked the logs there are no updates or other package is not installing and this the only package I created. Is ther any issue with hyper and base machine? Could you please help me on this? Thanks chandrakant.

Hi Prajwal, I have another issue, when i am deploying sccm client to VM using push method I am getting below error. I am using the default domain Administrator account and added same to Account option in sccm client installation method as shown in one of your forum but still the issue is persist. VMs are in domain and I am able to access the vm from UNC( machinename c$) Active directory, Sql, SCCM 2012, DNS, DHCP all are in one Base machine and using the account Administrator(Domain- chandru.com) Could you please help me on this. --->Attempting to connect to administrative share ' LAB1 admin$' using machine account. --->Failed to connect to LAB1 admin$ using machine account (5) --->ERROR: Failed to connect to the LAB1 admin$ share using account 'Machine Account' --->Trying each entry in the SMS Client Remote Installation account list --->Attempting to connect to administrative share ' 192.168.229.128 admin$' using account 'CHANDRU Administrator' --->WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account CHANDRU Administrator (0000052e) --->Attempting to connect to administrative share ' 192.168.229.128 admin$' using machine account. --->Failed to connect to 192.168.229.128 admin$ using machine account (5) --->ERROR: Failed to connect to the 192.168.229.128 admin$ share using account 'Machine Account' --->ERROR: Unable to access target machine for request: ', machine name: 'LAB1', access denied or invalid network path. Have you specified Client Push Installation account??

SCCM2012 R2 Software Deployment stuck at “Waiting for Content. Raising client SDK event for class CCM_Program. SCCM 2012 R2 Deployment Questions. Aug 27, 2015 Hi Prajwal, Thanks for beautiful information you share, I have installed the sccm 2012 on base machine(Server 2008 r2) and have VM(Hyper v) machine.

How to specify the Client Push Installation account • In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / - / Site Settings / Client Installation Methods. • To open the Client Push Installation Properties dialog box, double-click Client Push Installation. • In the Client Push Installation Properties dialog box, select the Accounts tab, and then click the New button. • In the Windows User Account dialog box, specify an existing Windows domain user account and password. You can repeat this process to specify as many accounts as you want. The accounts will be used in order until one succeeds.

This week I will do a small post about working with the restart behavior of installations in combination with the Application Model in ConfigMgr 2012. In previous versions there was sometimes a need to use a batch file to catch some weird installation return codes. The nice thing about ConfigMgr 2012 is that it gives us a possibility to specify those return codes and to react on it. In the rest of this post I will show in three steps how to configure ConfigMgr 2012 to work with return (restart) codes. Step 1: Return codes The first thing I always do is running the installation of an application a few times and see which return codes it gives me. Based on those experiences I create, if needed, some extra entries in the Return Codes –tab of the Properties of the Deployment Type.

By default the following return codes are pre-defined: • 0 – Success (no reboot) • 1707 – Success (no reboot) • 3010 – Soft Reboot • 1641 – Hard Reboot • 1618 – Fast Retry Step 2: Enforce specific behavior The second thing I do is determining how I think the client should react on the return codes. This can be configured, on the User Experience –tab of the Properties of the Deployment Type, by selecting one of values under Should Configuration Manager enforce specific behavior regardless of the application’s intended behavior? The following options are available (including small explanation): • Determine behavior based on return codes – (Default) The client will perform any action needed based on the return code of the application. • Note: In this case a good configuration in the first step is very important. • No specific action – The client won’t perform any action. Sdac Delphi 7 Rapidshare Movies. • Note: In this case it is possible to completely suppress a restart.

• The software install program might force a device restart – The client is told that the installation will force a restart. • Configuration Manager client will force a mandatory device restart – The client will always perform a restart. Step 3: Restart behavior The third, and last, thing I do is more a general client setting.

From the moment we decide to restart the device we should think about the configuration of the Computer Restart –settings in the Client Settings. The following Device Settings can be configured: • Display a temporary notification to the user that indicates the interval before the user is logged of or the computer restarts (minutes) – Default is 90 minutes. • Display a dialog box that the user cannot close, which displays the countdown interval before the user is logged of or the computer restarts (minutes) – Default is 15 minutes. Conclusion The combination of these three steps gives us a lot of options to work with the restart behavior of installations. In most cases the default configuration is perfect, but in some case some tuning is needed.

For example, the installation of an application is not allowed at any time. This can be achieved by either configuring a custom return code in the first step, or by specifying No specific action in the second step. Note: There are also Maintenance Windows and/ or Business Hours, that can influence the restart behavior. I didn’t mention them here, because, yes they can exist, but there should always be a moment that we “touch” a users’ device and this is about that moment.

The following note about “No specific action” is somewhat unclear: •Note: In this case it is possible to completely suppress a restart Does this mean that No specific action merely tells ConfigMgr to ignore a restart request by an application installer, or does it have some kind of super-power whereby it can suppress ANY attempt by an application to reboot the system? The note above would seem to indicate that it has the supreme power of suppression, but I think it may be just be inaccurately worded. I’m just trying to get a definitive answer on this.

Hi Peter, I use a vbscript to run an application with all the return codes you have mentioned set in the return codes tab and Determine behavior based on return codes selected. This script has dependencies which reboots and then the execution of the vbscript starts. It has two commands with noreboot command but while it succesfully runs the first one without any problems it reboots before the installation gets completed for the second command. So could it be a diffcode that i need to put in the return code tab or if i use a cmd that wrap the vbscript with whatever return codes to be presented as success to SCCM that would fix this?