Skip to main content

Posts

Showing posts from 2012

Software Update Management- SCCM 2012

The below post explains the end to end process of software updates management in SCCM 2012 Pre-requisites: 1.  WSUS Server (WSUS 3.0 SP2 ) should be installed on the SCCM site server or if you want to install WSUS on another server, it is important that you install WSUS administration console as the SCCM Server uses API. This  link explains the step by step procedure to install WSUS 3.0 SP2 2. Install SUP-Software Update Point on the SCCM Server . 3. Reporting Services Point: Install reporting services point role as described in this link . 4. Client agent: The software update client agent should be enabled(will be enabled by default) and the settings have to specified as per the requirement. On SCCM console, go to Administration>Site Configuration>Client settings>Right click on Default client settings> Click on Properties. If required, we can create custom client settings and then enable client settings for that settings. Unde

Hierarchy Maintenance Tool-Preinst

After the installation of Child Primary or child secondary , sometimes there will be issues with the key exchange( the newly installed site will not appear as “active” in the console) and we have to manually exchange the keys between the sites. Here we have to use Preinst.exe hierarchy tool to exchange keys : 1. Go to the child site, run preinst.exe with the command line argument /keyforparent Ex : preinst.exe /keyforparent 2. The /keyforparent option places the public key of the site in the file <site code>.CT4 at the root of the program files drive. After the preinst.exe /keyforparent is run , copy the <site code>.CT4 to the parent site’s \Inboxes\hman.box folder (not hman.box\pubkey) 3. On primary site, run preinst with the argument /keyforchild 4.The /keyforchild option places the public key in the file <site code>.CT5 at the root of the program files drive. You have to copy this file to the child site’s \Inboxes\hman.box folder (not hman

Determining BITS Version

Determining the Version of BITS on a Computer (Windows) To determine the version of BITS on the client computer, check the version of QMgr.dll. To find the version number of the DLL: 1.Locate QMgr.dll in %windir%\System32. 2.Right-click QMgr.dll and click Properties. 3.Click the Version tab. 4.Note the version number. If the DLL also exists in %windir%\System32\Bits, repeat the previous steps. BITS uses the DLL with the higher version number. The following table lists the versions of BITS and their corresponding QMgr.dll file version numbers. BITS version QMgr.dll file version number. BITS version QMgr.dll file version number  BITS 4.0 7.5.xxxx.xxxx BITS 3.0 7.0.xxxx.xxxx BITS 2.5 6.7.xxxx.xxxx BITS 2.0 6.6.xxxx.xxxx BITS 1.5 6.5.xxxx.xxxx BITS 1.2 6.2.xxxx.xxxx BITS 1.0 6.0.xxxx.xxxx 

Intro

Hi Friends,  This blog is to share ideas on various technologies and I would be posting information about SCCM , App-V, Windows, AD, SQL, Power Shell, Citrix and VDI. Let us help each other by sharing our knowledge.You can post here if you are interested in these technologies. Thank you.