You are browsing the archive for 2008 March.

Upgrading your sms 2003 admin skills to SCCM 2007

7:19 pm in ConfigMgr 2007, personal, SCCM 2007, SMS, Training by Kenny Buntinx [MVP]

Hi all,

As introduced during my presentation at the belgian techdays I will be teaching a custom training class on how-to upgrade you sms 2003 admin skills to SCCM 2007. This class is mainly aimed at current sms 2003 administrators that have transitioned to configmgr 2007 or are in the planning / preparation phase of transitioning.

This class is not about the upgrade / migration itself but on upgrading the administrator’s skillset. Quite a number of things have changed from Sms to Sccm and that’s what this class will focus on. Based on what you already know from sms2003 this class is meant to bring you up-to-speed with sccm 2007.

The idea is to make this a course that has lots of well-thought out hands-on-labs with clear instructions and examples that are usable in your production environment, mixed with me telling you everything I know about configmgr 2007.

More details on this class can be found here:

http://www.jcacademy.com/courses/_nl/coursesheet.asp?language=NL&country=&course_id=738

Summary:

What: Customized SCCM 2007 training class

Where: Jca Facilities in Louvain, Belgium

When: 28th till the 30th of April

How Much: The attendance fee for this course is 1250€

Instructor: Me, an enthusiastic sms trainer with a lot of training and field experience, and 3 Mvp awards.

Don’t wait too long, seats are going fast after the techdays announcement.

“Everyone is an expert at something”
Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS
http://www.scug.be/blogs/sccm

Building a great Virtual Machine

3:43 pm in Lab, Training, Virtual machine by Kenny Buntinx [MVP]

Hi all,

This post isn’t really sms 2003 or sccm 2007 related, but all of us tend to build virtual lab environments every once in a while. After some thinking I come up with some guidelines I will try to keep myself when building Virtual Machines from now on. This is the list I came up with so far.

  • Domain Name and Passwords should be keyboard agnostic (ie: be the same on azerty/querty
    • Domain Example: Contoso.net
    • Password Example: Topsecret
  • The lab layout should be set as the background image, like in the screenshot
  • The lab should contain the lab credentials set with bginfo
    • The saved parameters file and the windows background should be saved to a folder called c:\bginfo
    • Create login script with saved bginfo parameters file to run as login script.

Capture

 

 

  • The machine should allow you to shutdown/ restart from the ctrl-alt-del box
  • The welcome page should be disabled
  • System restore should be disabled
  • The shutdown event tracker should be disabled
  • password complexity should be disabled
  • Changing the computer account password should be disabled.
  • Screensaver should be disabled
  • Showing icons on the desktop should be disabled (you didn’t spend all this time on building backgrounds to have them cluttered with icons)
  • All passwords should be configured to not expire
  • Vm’s should be running on the latest service pack
  • Your last login should be with the user that the people will need in the lab so that it is prefilled when pressing ctrl-alt-del
  • the c:\drive should contain a folder called buildguide and an rtf file with the steps taken to create the vm, this way you can see what preparative action has been taken to make the labs work.

So I created my lab environment in visio and saved the different visio’s as bmp’s

And set a lot of the above options using a gpo, I backupped the gpo and saved it. The gpo can be found here:http://scug.be/files/folders/sccm/default.aspx

And you could obviously import it back on any domain controller using gpmc.

Enjoy

“Everyone is an expert at something”
Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS
http://www.scug.be/blogs/sccm

How to transition from sms 2003 to Sccm 2007 – Notes from the field Tips & Tricks

11:09 pm in ConfigMgr 2007, migration, SCCM 2007, script, SMS, Sms 2003 by Kenny Buntinx [MVP]

Hi all,


I delivered my session at the Belgian Techdays, and I promised on my blog and during the session that I would share the scripts with all of you. So here they come. Most of these scripts were used during a side-by-side upgrade transition. The side-by-side upgrade transition process looks like this:



  1. Install SMS 2003 SP2 on new server
  2. Attach new SMS 2003 SP2 site as a child site
  3. Let objects replicate
  4. Break Parent – Child relationship
  5. Upgrade new Site to Configmgr 2007
  6. Install KB945898
  7. Migrate clients to new site
  8. Remove boundaries from original site
  9. Add boundaries to new site
  10. Decommission original site
  11. Migrate non-replicating objects (queries/reports)

Benefits


This method provides a smooth transition without impacting your current sms 2003 infrastructure until your new Sccm 2007 environment is fully up and running and has been tested successfully. This makes it one of the lowest transitioning methods available.


Challenges / manual steps to perform in this method are



  1. Verify all objects have migrated
  2. Configure Site Settings
  3. Migrate Folders and folder membership
  4. Make Software distribution functional in new site without boundaries
  5. Optional: Modify package source path
  6. Migrate hardware inventory customizations (SMS_def.mof)
  7. Export / Import queries
  8. Export / Import reports
  9. Configure security rights
  10. Non-Replicating Software Metering Rules

In this section I will go over these challenges, and when available introduce a script to tackle these challenges. If a script is available I will first explain what the script does, give an example command line, and add some comments/remarks.


Challenge 1: See Script1 later in this post


Challenge 2: This is left as manual exercise for the reader


Challenge 3: See Script2 & Script3 later in this post


Challenge 4: See Script5 later in this post


Challenge 5: See Script4 later in this post


Challenge 6: See Challenge 2


Challenge 7: Use the export and import wizard, my experience has been that importing the mof file in one pass tends to be error-prone. I usually cut the mof file into 200KB chunks and import the chunks one by one, this has resulted in a much less error-prone import process. Run the script to move the queries into the correct folder, see script 3 later in this post.


Challenge 8: See Challenge 7


Challenge 9: See Challenge 2


Challenge 10: Software metering rules can be configured to apply to this site, or to this site and all child sites. If your software metering rules are configured to only apply to the current site than they will obviously not replicate. This setting is unfortunately not configurable after the rule has been created.


Scripts to Tackle the challenges:


Just for the record these Scripts do not come with any form of support or guarantee, the scripts have served me well but should be tested in your environment as your mileage may vary!!! Furthermore the script aren’t always the cleanest code, they don’t log a lot of data and do use some hardcoded parameters that would be more appropriate in an argument.


Script1: Countobjects.vbs


Description


This script counts the number of Queries, Reports, Packages, Advertisement, Software Metering Rules, Collections and folders.


Example


Usage: Cscript Countobjects.vbs


Remarks


You run this script on both the old and new sms 2003 servers and compare the numbers, once all numbers match up you can perform step 4 and break the parent – child relationship.


Script2: SmsContainers.vbs


Description


This script allows you to export and import the folder structure from one sms 2003 environment to another.


Example


Usage: Cscript SmsContainers.vbs export s01folders.txt or Cscript SmsContainers.vbs import s01folders.txt


Remarks


Because Sms 2003 does not replicate the folder structure to child sites we need a script that duplicates this folder structure. At import time this script creates a file called conversionarray.txt that allows us to translate old folder id’s into new folder id’s. We will need this file in later scripts to move the objects back into the correct folders.


 


Script3: xyzfoldermembership.vbs


Description


There are multiple scripts with this filename where xyz is either adv for adertisements, pkg for packages, rprt for reports, qry for queries and swmtr for software metering rules. These script move the respective objects into the correct folder.


Example


Usage: Cscript.exe xyzfoldermembership.vbs export S01xyzfolders.txt or Cscript.exe xyzfoldermembership.vbs import S01xyzfolders.txt


Remarks


These scripts need the conversionarray.txt to be available to find the correct folderid to place the objects in.


 


Script4: Modifypkgsource.vbs


Description


This script modifies the packagesource of all packages to a new server.


Example


Cscript Modifypkgsource.vbs


Remarks


If the sourcefiles for your packages are stored locally on the site server, you’ll need to modify the package sourcepath of all packages to a new server. First copy the source package folder structure to the new server and then edit the script to replace the oldserver and newserver strings with the values needed for your environment.


 


Script5: ModifyAdverts.vbs


Description


This script configures all advertisements to run from a remote distribution point.


Example


Cscript ModifyAdverts.vbs


Remarks


Because you cannot have overlapping boundaries we can only move the boundaries after all of the clients in a boundary have migrated. Because of this, clients in the new sccm infrastructure will not be able to find a local distribution point. So if you want these clients to be able to run advertisements these advertisements have to be configured to allow run from remote distribution point. If you want to change the value back later just change the bit value. Secondly if you already have some advertisements that are configured to run from remote dp, or download from remote dp, this script does not build a text file to store what it has changed, so the script doesn’t allow you to revert back to the original situation. If this is something you require you’ll have to adapt the script to save the original configuration.


The scripts can be downloaded here:


http://scug.be/files/folders/sccm/default.aspx



Enjoy.



“Everyone is an expert at something”
Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS
http://www.scug.be/blogs/sccm

How to transition from sms 2003 to Sccm 2007 – Notes from the field session at Belgian Techdays

7:54 pm in ConfigMgr 2007, SCCM 2007, SMS, Sms 2003, Training by The WMI guy

Hi All,

I will be speaking at the Belgian Techdays for the second year in a row. The session is aimed at current SMS 2003 administrators that are looking at transitioning to SCCM 2007.

The session is scheduled for Thursday the 13th of March running from 14:30 till 15:45. Because of time constraints the session will not include any demo’s. It will discuss all popular ways to transition from SMS 2003 to Sccm 2007, and introduce you to some scripts that can help you move to Sccm 2007 more smoothly.

Session Abstract:

This session will introduce you to the different methods of transitioning from sms 2003 to sccm 2007. The session will discuss the pro’s and con’s of the Wipe and Load, In-place Upgrade, Side-by-Side Migration and the speakers personal favorite the Side-by-Side upgrade. The session will also show you how you can use scripts to assist you in automating certain tasks during the migration process.

Hope to see you all there.

 

Enjoy.

“Everyone is an expert at something”
Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx