How to avoid duplicate GUIDs when you image System Management Server 2003 client computers

Do you really need that license logging service?  Doesn't look that way...

License Logging Service (LLS) is a tool that was originally designed to help customers manage licenses for Microsoft server products that are licensed in the Server Client Access License (CAL) model. LLS was introduced with Windows NT Server 3.51. By default, LLS is disabled in Windows Server 2003. Because of original design constraints and evolving license terms and conditions, LLS cannot provide an accurate view of the total number of CALs that are purchased as compared to the total number of CALs that are used on a single server or across the enterprise. The CALs that are reported by LLS may conflict with the interpretation of the End User License Agreement (EULA) and with Product Usage Rights (PUR). LLS will not be included in future versions of the Windows operating system.

If you use IBM hardware, and you happen to have a bunch of xSeries servers, and some of them happen to be x335 or x330's with the C2T cable management...

To be able to quickly and reliably switch between the servers in a stack, you need to create a new macro to count for you.  Let's assume you want to be able to switch to the 3rd server in the stack.  From your console you have to enter numlock, numlock, 0, 3, enter.  Easy enough, but depending on network conditions you may have to enter that a number of times before it actually takes. (Trust me this is frustrating.)  But you can create a macro that will do it for you. 

Simply go to - Macros: Configure...:  Create.  From there type in what you want to call it (I named mine “C2T 03” for this example). 

In the “Keystrokes” box enter the following:  <Num Lock><Num Lock>03<Enter> and  then hit ok.  This isn't the end though, because when you create a new macro it doesn't just pop into your list.  You have to edit the group or create a new group (which is what I recommend) so that you can add the new macro to your dropdown list.  If you have questions about this you can e-mail me and I will try to help you out.

It seems that it is indeed possible to deploy SMS packages to clients that aren't on your local network.  As long as your SMS server is reachable through the firewall on port 80, the clients will continue to report inventory information and recieve packages whenever they are connected to the internet.  The one big “gotcha” in this scenario...

Make sure your distribution point is also accessible from the interenet on port 80.  If your distribution point is on a file server that isn't accessible then you will be disappointed with the results.

This is my first entry on my new blog.  This blog was created by copying Rickey's work.  The software that is used is already evidenced by the “about” section of this page, so I won't bore you with the details.  I will tell you that I am currently running 2 blogs, to see which software I like best.  Fun huh?