Available at the Microsoft Connect site.
From now on you have everything to test Windows 7 Deployments via SCCM.
Don't forget to install SP2 (also beta) of SCCM as well!
Nico
vrijdag 26 juni 2009
dinsdag 12 mei 2009
OSD wipes the disk instead of formatting
Hi,
Did you ever noticed that if you change the advertisment distribution setting of your task sequence to "Access content directly..." your disk gets wiped instead of formatted?
The reason because of this is that MDT sets by default an argument on the "Format and Parition Disk" Task.
That argument looks like "_SMSTSDownloadOnDemand equals TRUE", if you remove this also your disk will be formatted when accessing the DP directly instead of downloading the content from the DP.
If you access the contect direcly you decrease the installation time significantly.
Nico
Did you ever noticed that if you change the advertisment distribution setting of your task sequence to "Access content directly..." your disk gets wiped instead of formatted?
The reason because of this is that MDT sets by default an argument on the "Format and Parition Disk" Task.
That argument looks like "_SMSTSDownloadOnDemand equals TRUE", if you remove this also your disk will be formatted when accessing the DP directly instead of downloading the content from the DP.
If you access the contect direcly you decrease the installation time significantly.
Nico
vrijdag 13 februari 2009
PXE issues - Part 2
Issue:
You get an IP address from your DHCP server but the system get stuck with contacting your PXE point, in the end you get a Vista boot error.
Solution:
Distribute always 64 bit to PXE point as well even for 32 bit machines
Almost all new computers these days are x64 capable even though you may only deploy a 32-bit operating system onto it. If the computer is x64 capable, then you must have an x64 boot image on the PXE Service Point, even if you are only planning to use a 32-bit boot image. The reason is that the PXE Service Point extracts certain files from the boot image that must be used in the very early stages of the PXE boot process. In this early stage, x64 files must be used on x64 capable hardware. Later in the process the PXE Service Point will determine that you want to use a 32-bit boot image and will revert to the 32-bit only code. But if you don't have the x64 boot image present on the PXE Service Point, it can't get past the early stages on x64 capable hardware.
You get an IP address from your DHCP server but the system get stuck with contacting your PXE point, in the end you get a Vista boot error.
Solution:
Distribute always 64 bit to PXE point as well even for 32 bit machines
Almost all new computers these days are x64 capable even though you may only deploy a 32-bit operating system onto it. If the computer is x64 capable, then you must have an x64 boot image on the PXE Service Point, even if you are only planning to use a 32-bit boot image. The reason is that the PXE Service Point extracts certain files from the boot image that must be used in the very early stages of the PXE boot process. In this early stage, x64 files must be used on x64 capable hardware. Later in the process the PXE Service Point will determine that you want to use a 32-bit boot image and will revert to the 32-bit only code. But if you don't have the x64 boot image present on the PXE Service Point, it can't get past the early stages on x64 capable hardware.
donderdag 15 januari 2009
SCCM and PXE troubles
Hi,
I suppose a lot of you have also troubles with WDS and SCCM.
Here you have a nice post, describing the issues I encountered.
http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/fb096553-22f8-4fe7-b326-a6bc7c126cb3
I suppose a lot of you have also troubles with WDS and SCCM.
Here you have a nice post, describing the issues I encountered.
http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/fb096553-22f8-4fe7-b326-a6bc7c126cb3
woensdag 12 november 2008
SCCM migration issues
Hello,
It's been a long time that I have posted something because I was very busy prerparing a SCCM migration by one of my clients.
The goal:
Upgrade SMS 2003 SP3 hierarchy.
One of the primaries was located on a VM Ware and this one needed to be migrated to a physical 64-bit machine.
Most issues I had was located on this primary.
I did first an in-place upgrade of the VM Ware.
The upgrade wizard failed all the time with fatal errors during the installation of the INBOX_MANAGER. After investigating for hours (I needed Microsoft support for this) we noticed that there were corrupt ct2 files in the hman inbox.
We removed the corrupt files and executed a site reset hoping that the wizard should continue installing the failed components.
Originally we thought SMS was working, but after a while I noticed all my clients had error 401 in their ccmexec.log. The complete SMS console was green so no issues following SMS. After some investigation again we discovered that IIS was running in 5.0 compatibility mode. Normally SCCM should change this but probably because of the failure of the wizard this task was skipped.
When trying to remove the limited status of IIS we noticed that the after IISRESET the option was always checked again. After some hours we discovered that the service "Internet Printing" was preventing IIS to stop this compatibility mode.
When removing the Internet Printing everything worked.
So far the in-place upgrade of the VM Ware...
The next weekend I had to move the VM Ware to physicall hardware.
I took an SMS backup with the "backup site" task.
When trying to restore this data with Site Repair wizard... gues what... FATAL ERROR.
After some attempts I gave it up and restored the SQL database manually.
The restore of the SMS data luckily succeeded via the Site Repair Wizard.
All SCCM stuff was working, only OSD was suddenly very slow.
This patch resolved the OSD issue:
http://support.microsoft.com/kb/955955
So this was a short description of my SCCM rumbles ;-)
The misery someone can have in case the wizard are failing...
It's been a long time that I have posted something because I was very busy prerparing a SCCM migration by one of my clients.
The goal:
Upgrade SMS 2003 SP3 hierarchy.
One of the primaries was located on a VM Ware and this one needed to be migrated to a physical 64-bit machine.
Most issues I had was located on this primary.
I did first an in-place upgrade of the VM Ware.
The upgrade wizard failed all the time with fatal errors during the installation of the INBOX_MANAGER. After investigating for hours (I needed Microsoft support for this) we noticed that there were corrupt ct2 files in the hman inbox.
We removed the corrupt files and executed a site reset hoping that the wizard should continue installing the failed components.
Originally we thought SMS was working, but after a while I noticed all my clients had error 401 in their ccmexec.log. The complete SMS console was green so no issues following SMS. After some investigation again we discovered that IIS was running in 5.0 compatibility mode. Normally SCCM should change this but probably because of the failure of the wizard this task was skipped.
When trying to remove the limited status of IIS we noticed that the after IISRESET the option was always checked again. After some hours we discovered that the service "Internet Printing" was preventing IIS to stop this compatibility mode.
When removing the Internet Printing everything worked.
So far the in-place upgrade of the VM Ware...
The next weekend I had to move the VM Ware to physicall hardware.
I took an SMS backup with the "backup site" task.
When trying to restore this data with Site Repair wizard... gues what... FATAL ERROR.
After some attempts I gave it up and restored the SQL database manually.
The restore of the SMS data luckily succeeded via the Site Repair Wizard.
All SCCM stuff was working, only OSD was suddenly very slow.
This patch resolved the OSD issue:
http://support.microsoft.com/kb/955955
So this was a short description of my SCCM rumbles ;-)
The misery someone can have in case the wizard are failing...
maandag 1 september 2008
donderdag 24 juli 2008
USMT - custom.xml sample
I needed to capture something out of the user profiles located under the hidden folders
local settings\application data\...
By default USMT skips these folders.
It took me a while to find this out, so it can might be interesstinf for one of you guys...
Here you have the sample. To make sure that this xml gets applied you need to add this /i:custom.xml as well in the loadstate and the scanstate command.
-
Lotus Notes
-
%CSIDL_LOCAL_APPDATA%\Lotus\Notes\Data
-
-
-
MigXmlHelper.DoesObjectExist("File","%CSIDL_LOCAL_APPDATA%\Lotus\Notes\Data")
-
-
-
#%CSIDL_LOCAL_APPDATA%\Lotus\Notes\Data\*
-
-
#%CSIDL_LOCAL_APPDATA%\Lotus\Notes\Data\*
local settings\application data\...
By default USMT skips these folders.
It took me a while to find this out, so it can might be interesstinf for one of you guys...
Here you have the sample. To make sure that this xml gets applied you need to add this /i:custom.xml as well in the loadstate and the scanstate command.
-
-
-
-
-
-
-
-
#
-
-
#
Abonneren op:
Berichten (Atom)
