June 2008 - Posts
Filtering on the GPEdit console will prevent the assignement GPO from displaying.
What you need
- Copy of ConfigMgr SP1 source files in expanded folder (SCConfigMgr07_UPD_EN)
- GPEdit.msc
Clean up for SP1:
- Open up GPEdit.msc
- Local Computer Policy / Computer Configuration / Administrative Templates
- Right Click Administrative Templates / Add/Remove Templates
- If they are previously installed remove the two ADM templates for ConfigMgr.
How to get them installed and displayed:
- Open up GPEdit.msc
- Local Computer Policy / Computer Configuration / Administrative Templates
- Right Click Administrative Templates / Add/Remove Templates
- Add the two templates from .\SCConfigMgr07_UPD_EN\TOOLS\ConfigMgrADMTemplates
- Go to View / Filtering
- Uncheck - Only show policy settings that can be fully managed
Thanks Christoper Stauffer for the filtering suggestion.
Question: I wonder what changed from RTM to SP1
When you finish your upgrade to SP1 do not forget to navigate to:
- In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / <site code> – <site name> / Site Settings / Client Installation Methods
- Right-click Software Update Point Client Installation, and click Properties.
As soon as the properties window opens you will be notified that the published version is not the newest. Your choices will be to ignore or to upgrade. Simple, but you have to do it.
Old Version: 4.00.5931.0001
Available Version: 4.00.6221.1000
Hey all,
I live in Cedar Rapids Iowa.
National news: CNN
Local news: KCRG
Last week was quite sporting, heavy rain fall, flash floods, levees breaking, road closures, and detours.
Fun Facts:
- Flood Stage is 12 feet.
- The big flood of 1993 peaked at 19.83 feet.
- Also known as the 100 year flood.
- Last week Thursday the Cedar River hit 31.18 feet.
- This went beyond the city’s 500 year flood plan.
- Current water levels according to NOAA
Good news, my parents were able to evacuate before the water really rose. They look forward to be able to return home this Friday (after 9 days). Not bad for city with water problems like the following pictures. My house is on high ground, however because they closed all roads except for one my daily commute went from 3 miles to just over 30 each way. Felt like I was in the metro area again (one reason I left).
Enjoy the pictures.
This link has a lot of aerial shots: http://www.andrealynnphoto.com/CRflood2008/
Note: I do not work for any of the compaines in these shots















Here is the situation. You need to find the SMS 2003 or ConfigMgr NameSpace in WMI and you don’t have the PowerShell expertise, yet. Easiest way is to use a GUI interface. Namely CIM Studio. CIM = Common Information Model… or framework of how info is stored in WMI.
About CIM Studio
http://technet.microsoft.com/en-us/library/cc181062.aspx
Download CIM Studio
http://technet.microsoft.com/en-us/library/cc181062.aspx
Note: I would recommend book marking CIM studio in IE. Saves time finding it later. Every time you launch CIM studio in IE6 and later you will need to accept the ActiveX object. Bookmark: C:\Program Files\WMI Tools\studio.htm
Question: Where do I look in WMI to find the SMS / SCCM info?
The default when you first open CIM Studio up is root\CIMV2. This is the local machine and CIM version 2.0 is the default location of machine information (think where the SMS_Def.Mof gets its info.) Have fun playing in there, but it is not where you want to be right now.
Question 2: Well that’s great, but how do I connect to a remote machine.. say the ConfigMgr server?
Connect to remote machine
\\<MachineName>\root
Example: \\ShaunWorkstation01\root
Note: do not add a trailing ‘\’ it will error out. WMI syntax is very exacting.
Pass credentials that allow you to have rights. Usually local admin.
The connection string above is a combination of machine and NameSpace.
NameSpace = root in the above example
Question 3: How do I find the NameSpace for the SMS / ConfigMgr information?
- Open __SystemClass
- Open __Namespace
- Click Instances button
One of the many results is: SMS.
Note: SMS is the correct namespace for any version of SMS or ConfigMgr (didn’t change with name change).
Great, now lets connect to the root\SMS name space: \\<server name>\root\SMS
Not a lot of results. Check the Namespaces again, you find:
- Inv_Schema
- Site_CAP (if this is an upgraded SMS 2003 server)
- Site_<sitecode>
So the WMI namespace I really want for SMS or SCCM is:
\\<ServerName>\root\sms\site_<SiteCode>
Example:
\\SMSServer01\root\sms\site_LAB
Fun thought, did you notice how the WMI classes never open in the same order. That just means the information returned is whatever is read first. Interesting.
Okay that is enough for this post. I’ll have another one us shortly about locating the Updates classes in System Center Configuration Manager 2007 SP1.
Just a random thought, but why is order of numbers on my keyboard's numpad
789
456
123
0 .
And the order of my phone keypad
123
456
789
*0#
Why aren't those in the same order?
**disclaimer**
The views opinions on this web log are mine alone and do not reflect my employer.
Why am I writing this disclaimer? This is a requirement. Plus it is true, I am writing here to help others so they can help me and we can all be better together.
Now that I have that out of the way, normal service will resume after the break. Enjoy!
By far one of the coolest 5 minute video's I've seen in a while. (last link is full video)
The ability to visualize and watch a magnetic field may potentially open new avenues of research. Plus it just looks so very cool.
or here:
Full movie here
HSBC, the world’s largest bank, online savings account division is running a special until August 15, 2008. The special is 3.5% APY. This is about .5% higher than most of the popular competition.
www.hsbcdirect.com
HSBC Direct, which was rated as the best online bank by Kiplinger’s Personal Finance, features no fees and no minimums (though it requires a $1 deposit to open an account). HSBC has traditionally been amongst the leaders in terms of interest rates.
I have been playing with Linux distribution Fedora 9. However, I cannot get it to install in my Microsoft Virtual Machine 2007 running in x64 Windows Vista Ultimate SP1. The CPU is a dual core socket 939 Opteron on an Nforce4 motherboard.
The error I am recieving is i1586 core does not exist. You better believe it doesn't. See the picture below.

I did find several posts in forums that state older x64 processors would be discovered as x32 virtual environments. What makes it really odd is they suggest running the i386 edition of Fedora 9.
You can get fedora 9 here: http://fedoraproject.org/get-fedora.html
You can read about some great virtual machine 2007 fixes here: http://blogs.technet.com/seanearp/archive/2008/05/19/installing-fedora-9-sulphur-in-virtual-pc-2007.aspx
Hopefully, i'll be able to post that the i386 edition works.
|
|
RTM |
SP1 |
| Type |
Primary |
Primary |
| Version |
4.00.5931.0000 |
4.00.6221.1000 |
| R2 Installed |
|
No |
| Build |
5931 |
6221 |
R2 Installed property is not present in RTM version. I would guess R2 won’t work with RTM.
Note: Translation of Initialisms and Acronyms
- RTM
- Release To Manufacturing.
- This is the initial product launch release before any service packs or add-ons
· ConfigMgr or SCCM
o System Center Configuration Manager 2007
· R2
o Release 2
o Microsoft nomenclature for major product enhancement not including security, hotfixes or patches.
· Initalism
o First characters of words but not pronounced as a word
o ex. FBI
· Acronym
o First characters of words that are pronounced as a word
o ex. SCUBA
Background: All programs and server applications are not stored on the OS partition. During the RTM the WAIK was installed on the E drive. During the ConfigMgr 2007 SP1 upgrade process:
- WAIK was uninstalled automatically
- WAIK was attempted to automatically install using default settings.
When the upgrade attempted to reinstall the WAIK it defaulted installed to the default OS drive. This failed on my server. The WAIK requires 1.25 GB of free space to install. Work Around:
- Before attempting to run SP1
- Uninstall WAIK via ARP (Add Remove Programs)
- Install WAIK via the new copy in:
- . \SCConfigMgr07_UPD_EN\SMSSETUP\WAIK\
- Run the SCCM SP1 upgrade again