Share: Home
VirManSec Foundation – Episode 2 - Asem Alhourani - VirManSec Community
VirManSec Community

Announcements

VirManSec Foundation – Episode 2
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!

After we agreed about the general vision, and after I thought about what I want to see in this community and how I want this community to look like, and what are the goals and expectations. I wanted to purchase a hostname.

I browsed the internet and found some useful sites that provide guidance on how to purchase a domain name, and how to reserve it to your organization. Looking for a faster answer I had to contact the experts in this field, so I contacted my friend Fadi AlNaaji who told me to go to www.name.com and purchase the domain name from there. And then I purchased the name www.virmansec.com for two years.

We considered this very small step as a major milestone in our community foundation progress. This moved us by that time to start creating a logo for our community. This was one of the interesting parts of founding the community where I told my work colleague Ahmed Adel Ahmed to contribute in designing a logo for us, and gracefully he did so. And I would like to thank him for his very elegant designs. Nevertheless my friend Gheyath Huzayen, a world class designer (see links about G in the bottom of this page) contributed to do the design, and he designed this current very elegant and professional looking design. I would like to thank him too on behalf of all the community members.

So we thought, the domain name was purchased; the logo was prepared and approved by most of the community board members, now we need to host our community server!! And this is when I spoke with IT decision makers who can sponsor and host a server within their own data center or even at an ISP site, but I wasn’t lucky convincing them about the importance of such a community. However, I was glad that I know the owner of an excellent mid-size company called (R-Tech)* which is owned by my friend Mr. Nour Homsi who was so enthusiastic about the whole idea of community and knowledge transfer, because Nour’s company is a IO related company in addition to being a Microsoft certified training center. R-Tech proposed to host VirManSec IT community website and Nour gave us a Hyper-V Virtual Server. We would like to thank him for his continuous efforts to sponsor the community. And yes, this community website is hosted on a Virtual Server!

After we got the server and the real IP address we sent all the information to Fadi AlNaaji again who collected all this puzzle pieces to publish the website in the global DNS, he did many more additional tasks in this regard that I really value but I cannot recall. We would like to thank Fadi for his contribution into this community.

In the coming episode I will tell you how I met the creative mind behind designing the community web site who also happens to be our web site administrator.

* Here is the websites of the G & R-Tech

Gheyath http://www.rebaldy.com/

R-Tech http://www.r-tech.com.sa/


Posted 03-16-2009 5:00 PM by Asem Alhourani

Comments

Fadi_alnaaji wrote re: VirManSec Foundation – Episode 2
on 04-07-2009 3:24 PM

It was nothing Asem, it was an honor to contribute in launching this community..

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