frode's notes
A collection of not-so-useful information…
ConfigMgr 2007 R3 Release Candidate available
Aug 5th
The ConfigMgr R3 release candidate is now available from Microsoft Connect. The big thing in R3 is the green theme, with power management and reporting.
Check out the list of features over at the System Center Team Blog.
Microsoft Deployment Toolkit 2010 Update 1 available
Jul 20th
Good news. MDT 2010 Update 1 is now available. For those of you who used Modena previously, this addon has now been incorporated into MDT under the name User Driven Installation (UDI), and can be integrated with ConfigMgr. The update also includes support for ConfigMgr R3 Pre-stage media.
Read more about it at the System Center blog, or download it from Microsoft Connect.
Blog back online again
Jul 10th
Had a little server crash, so the blog has been offline for some time. It’s now back 
Monitoringhost.exe consuming 100% CPU, OpsMgr 2007
May 13th
I just realized my Hyper-V host had an old OpsMgr 2007 Agent from when I was testing it in my lab. Also, the hostmonitoring.exe service consumed most of the CPU, making the guest VMs pretty sluggish. I didn’t need the OpsMgr Agent, so I just uninstalled it. If you do use OpsMgr 2007 to monitor your hosts, there is a fix for the issue with it using 100% CPU.
Check out this KB from Microsoft.
ConfigMgr PXE TFPT Download loop
May 7th
Getting the following on your PXE boot in ConfigMgr?
Downloaded WDSNBP…
Contacting Server (xxx.xxx.xxx.xxx)
Architecture: x64TFTP download SMSBoot\x64\pxeboot.com
.
TFTP download SMSBoot\x64\pxeboot.com
.
TFTP download SMSBoot\x64\pxeboot.com
and looping?
Check if the <drive>\RemoteInstall\SMSBoot\x64 folder contains the right boot files. Sometimes the folder can be empty, and you need to copy the files from <drive>\RemoteInstall\Boot\x64 folder.
ConfigMgr 2007 R3 Beta Install needs Eval version, by Design says Microsoft
Apr 28th
Microsoft recently released ConfigMgr 2007 R3 Beta, and it has been available for download at Microsoft Connect.
However, there seems to be some problems installing the beta for some users, including myself. What happens is that when trying to run the installer there is an error message saying that the evaluation version of ConfigMgr SP2 or higher is required, and it simply won’t install.
The weird thing is that the logfile for the R3 Beta install says that R3 is already installed, which threw me off.
Logfile says following:
Property(C): SmsDetectDowngrade_ErrorMessage = A more recent version of the application is already installed. Setup will now end.
Property(C): SmsDetectUpgrade_ErrorMessage = Configuration Manager 2007 R3 is already installed. To install this version please uninstall the previous version by using Add or Remove programs.
Since I didn’t have R3 installed, and had the required “SP2 or higher”, I immediately figured that the installer was broken and contacted Microsoft to report the issue.
After the Microsoft technician had talked to the ConfigMgr production team, he answered the following, which clears things up.
Hello,
I discussed this with our product team and in order to ensure licensing compliance with the pre-release software that is presented to our Open Beta customers we have to ensure the R3 feature pack release software cannot be installed into a production environment and violate licensing and terms of use, hence the need to install on an Eval version of SP2. Our TAP customers will be receiving a different version of the R3 package that will allow them to install into a production environment as per our requirements for proper testing and evaluation of the pre-release code. Our TAP customers are given a Supplemental EULA that provides them the rights to do so. I am sorry for any complications this may cause with your testing of the software! Thank you again for your time and feedback.
This basically means that you can’t install the R3 Beta in a production environment, and need the actual evaluation version of SP2 (as the error message clearly states) to install it.
ConfigMgr 2007 R3 Beta Relased
Apr 23rd
Hi folks. ConfigMgr 2007 R3 Beta has now been released by Microsoft. Head on over to Microsoft Connect to get your copy today.
Some features in R3:
- Power Management. Provides a set of tools to allow the site administrator to configure standard Windows power settings across computers
- Operating System Deployment Enhancements. Prestaged Media is a way to integrate with OEM factory imaging in order to leverage imaging at the OEM to speed up new hardware deployments
- Dynamic Collection Evaluation. Allows you to more rapidly evaluate a collection membership by adding only newly discovered resources.
- Delta Discovery. Performs an intermediate discovery cycle adding only new resources to the Configuration Manager 2007 database.
- Collections. Allows you to search for and add resources to the specified collection.
- Desired Configuration Management. Allows you to easily create collection of compliant or noncompliant computers in desired configuration management.
- Supported Clients Per Hierarchy: Configuration Manager 2007 R3 supports up to 300,000 clients per hierarchy when using the default settings for all Configuration Manager 2007 features. This increase in supported clients is the result of improvements to the Active Directory synchronization and Collection Evaluation processes.
Source: Microsoft. Check out Microsoft Connect for a full description of the new features.
Installing Apache, PHP and MySQL on Slackware 12.1, a Quick Guide
Apr 21st
While I am pretty much a Microsoft guy today, I fiddled quite a lot with Linux, and especially the Slackware distro back in the days . I recently threw away my old file server, that ran Linux (Slackware 12.1), and replaced it with some new hardware and Hyper-V.
Since I like to keep up to date on stuff I’ve been doing in the past, I decided to set up a new Linux guest on my Hyper-V, and while I won’t go through the basics of installing the OS, I decided to write a short guide to install Apache, PHP and MySQL on Slackware 12.1 to get a web server with a database back-end up and running. I also decided I might as well post it here, and as this is written for Slackware 12.1, it will probably work for previous releases (I think I’ve used this method since 9.0), and also the latest 13.0 build. Remember that this is a quick guide, so if you need to do more customization you will have to go elsewhere (preferably read the docs).
So here goes.
ConfigMgr PXE-settings for remote DHCP server
Apr 20th
Add the following DHCP Scope Options:
060 PXEClient
066 IP Address of WDS Server
067 boot\x86\wdsnbp.com
These are required steps if your DHCP Server is on a different subnet than your SCCM/WDS/PXE Server.
Here is are some good KB Articles on this subject – http://support.microsoft.com/default.aspx/kb/926172 and http://technet.microsoft.com/en-us/library/cc732351.aspx
Stolen from Paul Jones Notes from the Field.
Recent Comments