Share: Home
The crazy 88 - Asem Alhourani - VirManSec Community
VirManSec Community

Announcements

The crazy 88
Asem Alhourani

Syndication

News

  • When you’re going to deploy a new package with SCCM 2007, there are a few steps you need to follow. The easiest way to deploy a package is to follow the next steps: [Y] 1.) Collection 2.) Package 3.) Program 4.) Distribution Point 5.) Advertisement Before we are going to deploy Office 2007, we’ve to create a MSP file for customize the Office 2007 installation. You can start the Office Customization Tool using the following command: Run ---> setup.exe /admin. Save the file in the updates folder on your Office 2007 source directory Step 1, creating a collection: 1.) Create a new collection, to specify the computers where Office must be installed. 2.) Navigate to System Center Configuration Manager, Site Database, Computer Management, New Collection 3.) Give your new collection a name, for example “Office 2007 Enterprise” 4.) On the Membership Rules dialog box, Create a collection Packages can only be distributed to members of a collection. A collection can contain multiple computers, a single computer, a single user and members of a security group. Configuration Manager 2007 operates with two different types of collections. · Direct membership based. ü Click the computer icon, which opens the Create Direct Membership Rule Wizard. Click Next ü On the Search for Resources dialog box, click the Resource class drop-down menu and select System Resource. Then, click the Attribute name drop-down menu and select Name. In the Value field enter %, and then click Next ü On the Search for Resources dialog box, click the Resource class drop-down menu and select System Resource. Then, click the Attribute name drop-down menu and select Name. In the Value field enter %, and then click Next ü On the Collection Limiting dialog box, click the Browse button, select All Windows Workstation or Professional Systems, and then click Next ü Select the computer(s) you want to deploy Office 2007 and click Next.,, Finish · Query Based collections are use full when distributing software to a larger group of resources based on specific criteria’s Example, all workstations in Copenhagen or computers belonging to an Active Directory security group. Direct membership collections are use full when distributing software to a narrow group of resources e.g. 5 test pc’s. Step 2, creating a package: 1.) Navigate to System Center Configuration Manager, Site Database, Computer Management, Software Distribution, Package, New Package 2.) On the General dialog box of the New Package Wizard, enter the Name, Version, Manufacturer, and Language. For example, Office, 2007, Microsoft, English (US) 3.) On the Data Source dialog box, select This package contains source files. Click the Set button, and then enter the path for the location of the source files in the Source directory field. For example E:\Software\Office 2007\, which contains a copy of the 2007 Office Enterprise installation CD. 4.) Click OK, and then continue to click Next and accept the default settings on all of the following dialog boxes: Data Access, Distribution Settings, Reporting, and Security. On the Wizard Completed dialog box. Step 3, creating a Program: 1.) Navigate to System Center Configuration Manager, Site Database, Computer Management, Software Distribution, Packages, Office 2007, Programs, New, Program 2.) Give the new program a Name 3.) On the Command-line box, type in setup.exe 4.) On the Environment dialog box, click the Program can run drop-down box and select Whether or not a user is logged on. This will enable Run with administrative rights for the Run mode. Leave the default for Drive mode to Runs with UNC name, and then click Next (Because the customization file, CustomOffice.MSP, was placed in the \Updates folder, a command line option is not needed to reference its location) 5.) On the Advanced dialog box, select the check box for Suppress program notifications, and then click Next Step 4, Copy to Distibution points: 1.) Navigate to System Center Configuration Manager, Site Database, Computer Management, Software Distribution, Packages, Office 2007, Distribution points 2.) Manage Distribution Points 3.) Select “Copy the package to new distribution points” 4.) Select the distribution points 5.) Click finish and wait a copple of minutes 6.) Check the status changing from Install Pending to Installed Step 5, creating the advertisement 1.) Navigate to System Center Configuration Manager, Site Database, Computer Management, Software Distribution, Advertisements 2.) New Advertisement 3.) Give the advertisement a Name 4.) Select the package, Program and Collection 5.) Click finish and wait a copple of minutes 6.) On the client wait for the next Machine Policy Retrievel & Evaluation Cycle After the setup is finished, Office 2007 is deployed to your client(s) and is ready to use!


‘Updated Prerequisite Components’ page in the installation wizard of Microsoft System Center Configuration Manager will require that you choose between installing the required 88 updates automatically in case the box you are using to install SCCM 2007 is connected to the internet. On the other hand, there is another option that indicates that the installer had already prepared & installed the latest version of the software updates prerequisite.

Working on an MSF phase at the customer’s site requires that we go through a testing and proof of concept phase, this phase usually and preferably is implemented completely in an isolated environment; hence in most cases, the whole lab setup is not connected to the internet.
Inspired by the movie ‘Kill Bill Vol. 1’ I’ve called those updates the crazy 88! Remember the Japanese 88 guys who were trying to take down Kiddo (Uma Thurman)? You can simply download the 88 updates prior to the installation of SCCM 2007 to local or network path on your site server by going through the below steps:

Create a new folder, I like to call it ‘Manifest’
From the installation source of the SCCM 2007 run the below command line
Setup.exe /download DriverLetter:\Manifest
Eventually this will download updates starting with a file called ConfigMgr.Manifest.cab which happens to have the latest version of the software updates. If you try to extract ConfigMgr.Manifest.cab you will find in the extracted xml file at the header the version of the SCCM 2007 supported, look below for an example
<_versioninfo>
Config Mgr 2007 RTM
1.00

Bottom line, you can download the files as mentioned above on a computer that has an internet connection, then copy the whole folder to an ultimate box (destination) and start the installation procedure of SCCM 2007 by selecting that you’ve manually downloaded the updates to an alternate location.
Also, if you know that it will be hard to get an internet connection at the customer's site or that you know that the customer's internet connection is considered humble; you can do what was described above at your company site.


Posted 02-09-2009 1:21 PM by Asem Alhourani
Share:
Sponsors: Ms Logo Rtech Logo Pixel Arabia Logo Effate Univercisty Logo NC Logo
Home | About us | Contact us | Support
VirManSec IT Community, All Rights Reserved 2010