Nico's IT Rumblings

New Blog Page

2011-04-26T16:34:00.000+02:00

I will not use longer this blog page.

You can find my new blogs on: http://scug.be/blogs/nico

Nico

Be carefull with IPv6

2010-12-16T10:02:00.005+01:00

I encountered the following with a customer, software was MDT 2010 update 1 used for LTI deployments.

At the end of the capture sequence the "Apply Windows PE" task was failing.

The log files didn't not tell much more then the screenshot. After some investigation I noticed my deploymentshare was responding with an IPv6 address.

The reason was that the traffic was going via the ISATAP router because the customer had Direct Access and UAG running.

To workaround this I disabled the IPv6 protocol during the capture process on the NIC

Remote Control Global Settings

2010-06-09T14:42:00.003+02:00

With SCCM you can specify Remote Control Settings, unfortunately these settings are site settings so all the machines within your sites will have the same remote control settings.
So for instance, the setting that you prefer a pop-up that a user needs to allow you before you can remote control his machine...
Well this settings caused a challenge for me, as I got a group of critical kiosk machines that I want to take over remotely but I don't want that users have to allow me first.

From what I have heard within vNext we will be able to set Remote Control settings on each collection, this is awsome but for the moment with SCCM we need to workaround this.
How?

First scenario is to override the ‘Ask for permission when an administrator tries to access the client’ setting part of the Remote Tools Client Agent.
The following code is what the ConfigMgr client receives from the Management Point (T01 is the sitecode in this example):
instance of CCM_RemoteToolsConfig
{
PolicyID = "{GUID value}";
PolicyVersion = "x";
PolicySource = "SMS:T01";
PolicyRuleID = "{GUID Value}";
PolicyInstanceID = "{GUID value}";
Enabled = TRUE;
ComponentName = "SmsRemoteTools";
Type = 1;
RemoteToolsEnabled = TRUE;
AllowChat = TRUE;
AllowClientChange = FALSE;
AllowFileTransfer = TRUE;
AllowReboot = TRUE;
AllowRemoteExecute = TRUE;
AllowTakeover = TRUE;
AllowViewConfiguration = TRUE;
AlwaysVisible = FALSE;
AudibleSignal = TRUE;
CompressionType = 2;
ControlLevel = 2;
DefaultProtocol = "TCP/IP";
IndicatorType = 0;
PermissionRequired = 1;
UseIDIS = TRUE;
VisibleSignal = TRUE;
DisableToolsOnXP = TRUE;
ManageRA = TRUE;
EnableRA = TRUE;
AllowRAUnsolicitedView = TRUE;
AllowRAUnsolicitedControl = TRUE;
ManageTS = FALSE;
EnableTS = FALSE;
EnforceRAandTSSettings = TRUE;
PermittedViewers = NULL;
};
Note the PermissionRequired settings is set to 1 which states that permissions are required when running Remote Tools.
This is the value we have to overwrite by creating a new mof file.
The mof file will look like this:

#pragma namespace("\\\\.\\root\\ccm\\policy\\machine\\requestedconfig")
[CCM_Policy_PartialPolicy(true)]
instance of CCM_RemoteToolsConfig
{
// Header properties
PolicyID = "1";
PolicySource = "local";
PolicyVersion = "1";
PolicyRuleID = "1";
PolicyInstanceID = "1";
Type = 1;
// Data properties
[CCM_Policy_Override(TRUE)]
PermissionRequired = 0;
};

Watch the "PermissionRequired=0"

We save this file as for instance CustomRemoteControl.mof.

On each machine you want that the default settings gets overwritten with the new one you need need to compile this new mof file.

You can do this with:
%windir%\system32\wbem\mofcomp.exe CustomRemoteControl.mof

Upgrade to SCCM R3 (beta) - Issue with KB977384

2010-05-17T11:46:00.002+02:00

I'm running SP2 R2 without issues and my version of the site server in the SCCM console is 4.00.6487.2000.

When trying to install the hotfix that is a prereq for R3, I got the error that my version of ConfigMgr is not valid..??

"The hotfix is not valid for this version of Configuration Manager 2007"

If I enable logging on the KB I get this version. - '4.00.6487.2700' This is indeed the version with ICP2 installed.

So more probably the International Client Packs is causing this. Installing the hotfix on a server without ICP works fine.

This is quite an issue as ICP's cannot be uninstalled.

I reported this to MSFT to make the version check a little bit more flexible.

Installing SCCM on Server 2008 machines

2010-05-12T10:08:00.002+02:00

With IIS 7.0 (Server 2008) and IIS 7.5 (Server 2008 R2) there are some extra modifications you have to do to get SCCM up and running.
These are the ones I have encountered through the projects I did.

Install and enable webdav:
http://learn.iis.net/page.aspx/350/installing-and-configuring-webdav-on-iis-70/

RDC missing on Windows 2008:
http://www.windows-noob.com/forums/lofiversion/index.php/t487.html

Unable to install MP Control Manager and MP:
Check MPsetup.log, probably some webdav settings are wrongly set (true\false) and
an Authoring Rule was not created.
Allow property queries within infinite depth should be true
Allow custom properties should be false
Allow anonymous property queries should be true
Create Rule – Allow All users read to acc to all content

Install ASP to get Reporting to work.

With SQL 2005 on Server 2008:
------------------------------

http://support.microsoft.com/kb/920201
http://www.microsoft.com/downloads/details.aspx?FamilyId=FB0EE17E-96EB-4CBB-AC09-95A4DCF73077&displaylang=en

With SQL 2008 on Server 2008 no issues encountered (yet). :-)

SCCM Computer Association - keep same hostname

2010-05-10T11:19:00.007+02:00

In a Replace Scenario, so when migrating from one machine to another one, you need to associate machines with each other in SCCM. This to make sure User Data gets restored correctly (State Migration Point). Some customers have choosen to keep the same hostname mostly because of machine names are linked to AD Security Groups.

This is an issue in the Computer Association wizard. As the wizard is expecting 2 different hostnames.

To workaround this you can enter a Dummy hostname for the new Machinne.

Now we can continue with wizard to associate machines with each other and to add the new machine to a collection where a Task Sequence is advertised.

Imagine we start to install the machine at this point, the hostname of the machine will be "SCCMDummy". So we have to do something extra.
We need to put a variable on the SCCM machine record that will make sure that OSDComputerName (SCCMDummy) will be overruled with the value that we want.
If you work with an MDT database you can put the value in the database of course.

To completely automate this you can find excellent example scripts in the SDK.

Migrate Windows 2000 machines to Windows 7

2010-05-04T21:28:00.002+02:00

You shouldn't expect it but a lot of companies still have Windows 2000 machines running and some will ask to migrate. Migrating these machines with USMT (refresh or replace scenario) is not supported by Microsoft nevertheless it works. The supported way is to upgrade first to XP and then to Windows 7. You can already imagine how your customer will react if you will propose this migration track :-)

So, it works but there are some caveats though:

- USMT 4 will not run in a Windows 2000 shell, you can workaround this by running your scanstate command in Windows PE Shell. Short, you need to create a TS that will advertise your refresh scenario which will prestage Windows PE\Machine will reboot\Start up in Windows PE\Run scanstate\format disk\apply WIM\...

- Format Disk?? Yes. Hardlink doesn't seems to work. At least hardlink works but with this you need to wipe the disk as the MININT folder has the data on board. Well, wiping the disk was not really a success. When wiping the disk the installation of Windows 7 always failed. During the first reboot in Windows 7, the installation stopped with a fatal error probably because of NTFS issues..
When formatting the disk the installation of Windows 7 was a succes.

- SMP cannot be used as the task "Request State Store" does not work in Windows PE. So the variable %StateStorePath% needs to be specified in your USMT command.

Suppress SCCM notification for App-V

2010-04-23T14:19:00.003+02:00

Since R2 App-V is strongly integrated into SCCM.

A most common scenario will be that for instance a user logs on and the icon of avirtual application appears automatically on his desktop, ready to stream the application.

Default, you first get a notification (balloon in system tray) that the user has to click before the icon appears on its desktop.

That's probably something you don't want to have. You probably prefer if the user logs on the icon will be available without user interaction.

As you might know you can suppress notification with SCCM on programs of SCCM packages... BUT App-V Packages do not have programs, so we cannot select this option.

At this point some scripting will be required.
With following script you suppress notifications for App-V packages.

strSMSServer = "."
strPackageID = "XYZ00001"
strProgramName = "[Virtual application]"

Set objLocator = CreateObject("WbemScripting.SWbemLocator")
Set objSCCM = objLocator.ConnectServer(strSMSServer, "root\sms")
Set Providers = objSCCM.ExecQuery("SELECT * From SMS_ProviderLocation WHERE ProviderForLocalSite = true")
For Each Provider in Providers
If Provider.ProviderForLocalSite = True Then
Set objSCCM = objLocator.ConnectServer(Provider.Machine, "root\sms\site_" & Provider.SiteCode)
' strSMSSiteCode = Loc.Sitecode
End If
Next

Set objProgram = objSCCM.Get("SMS_Program.PackageID='" & strPackageID & "',ProgramName='" & strProgramName & "'")

ProgramFlags = objProgram.ProgramFlags
WScript.Echo "Flags for " & strPackageID & ":" & strProgramName & " currently set to " & ProgramFlags
WScript.Echo "Adding 0x00000400 (COUNTDOWN. The countdown dialog is not displayed)" ' see ConfigMgr SDK for details ("SMS_Program Server WMI Class")
ProgramFlags = ProgramFlags + 1024
WScript.Echo "Set flag to: " & ProgramFlags
objProgram.ProgramFlags = ProgramFlags
objProgram.Put_

Enjoy!

Conigurations in bootstrap.ini are not applying

2010-01-06T14:28:00.003+01:00

I've seen recently a lot of posts on forums of people that are having issues with their bootstrap.ini.

In other words if they change something to the ini file it does not get applied.

Well for once an for all, as bootstrap.ini gets executed in a very early stage during WinPe it's required that you create a new WinPe Installation CD each time you added some changes to bootstrap.ini.

So -> Change bootstrap.ini = New WinPE Installation CD

MDT Wait for correct IP Address

2009-09-28T09:33:00.003+02:00

It can happen when executing an LTI deployment that you get an error that your Deployment Share is not available.

If you hit F8 to open a DOS box and you notice you don't have an IP address (yet).

I have a trick how you can extend a bit the time for MDT to acquire an IP address.

I saw this already with several customers if they had some latency on their network cause by DHCP, network components,...

What you have to do is the following:

You mount your current boot image with imagex. (/mountrw)

Go to startnet.cmd and edit

Once you open the file in notepad the only contents will be the command:
wpeinit

Change the file to contain the following:
wpeutil InitializeNetwork
ping localhost (You could ping the WDS server too)
wpeinit

Save you changes of the cmd file.

Unmount the image and save your changes of the image. (/unmount /commit)

Burn this updated image to a new Installation CD or publish this image back to your WDS.

Your network issue should be solved now.

Dynamically install drivers with MDT 2010

2009-07-28T10:34:00.005+02:00

MDT 2010 has some nice new features, one of them are Selection Profiles.

Like Michael describes on his blog Selection Profiles can be used for several things into MDT.

http://blogs.technet.com/mniehaus/archive/2009/07/12/mdt-2010-new-feature-18-selection-profiles.aspx

Another nice thing to use Selection Profiles for is to install drivers on a dynamic basis.

Create a driver folder structure into MDT. Then create a Selection Profile and call it like the respectively model names. You can read the model name out of WMI by executing:
CMD -> WMIC
CSProduct Get Name

In CustomSettings.ini you just add:
DriverSelectionProfile=%model%

OR

If you don't want to create a Selection Profile for each model you can create a rule that checks the dirver structure:

DriverGroups001=%Model%

(remark: if you build your Driver structure you need to call the folders like the WMI product name - cf. like we did with Selection Profiles)

MDT Database connections wit MDT 2010

2009-07-17T13:41:00.002+02:00

If you encounter issues connecting to the MDT database, do the following for troubleshooting.

Put following files into one folder:

ztigather.xml
ztigather.wsf
customsettings.ini (where you specifiy the connection to the DB)
ztiutility.vbs
ZTIDataAcess.vbs

Execute following command from a host that needs to connect to the DB.
cscript ztigather.wsf /debug:true

Most common issues are SQL permission or Named Pipes that isn't enabled in SQL.

MDT 2010 Beta 2

2009-06-26T08:33:00.001+02:00

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

OSD wipes the disk instead of formatting

2009-05-12T13:10:00.003+02:00

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

PXE issues - Part 2

2009-02-13T17:08:00.001+01:00

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.

SCCM and PXE troubles

2009-01-15T14:25:00.001+01:00

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

SCCM migration issues

2008-11-12T08:37:00.002+01:00

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...

Holiday!!

2008-09-01T00:50:00.001+02:00

Finally a well deserved holiday

3 weeks west coast in the VS

USMT - custom.xml sample

2008-07-24T14:01:00.001+02:00

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\*

Move of blog

2008-07-23T19:27:00.002+02:00

Hello

Just to inform you that this blog will be moved soon to

http://myitforum.com/cs2/blogs/nsienaert/default.aspx

People of ITForum asked me to create my blog on their domain.
What's a big honour off course!

Hope to see you guys there!

Nico

Fatal error during upgrade to SCCM SP1

2008-06-06T16:11:00.002+02:00

First of all check the configmgrsetup.log file.

If SCCM and WAIK are not installed on the OS driver (another partition)

and you receive 1603 error during the Waik Installation, this is the reason:

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.

Solution

Before attempting to run SP1
Uninstall WAIK via ARP (Add Remove Programs) (if the previous attempt of SP1 hasn't done it for you)
Install WAIK via the new copy in: . \SCConfigMgr07_UPD_EN\SMSSETUP\WAIK\
Run the SCCM SP1 upgrade again

ZTI ERROR - Unhandled error returned by zticonfigure: Object required (424) and Unable to find CustomSettings.ini, rc = 1

2008-05-26T08:49:00.003+02:00

If you can find this errors somewhere in you log files you are probably refering in your CS.ini to a database value that does not exist.

Example:

In the past I used the column keyboardlocale in BDDAdminCorDB. In my CS.ini I had a line keyboardlocale=%keyboardlocale%

I removed the column because I use 'InputLocale' in place, but I forgot to remove the line out of CS.ini.

The result was that the "configure" action was hanging without prompting any error and my ztigather.log showed the errors of the title of this post.

After spending some days of troubelshooting I discoverd this was the root cause.

zti error opening sql connection: cannot initialize sspi package

2008-05-20T19:49:00.003+02:00

When this error appears in your ztigather.log you have to add security.dll to your winpe.wim image of WAIK 2.0 to make a named pipe integrated security connection possible.
You can find the dll in the system32 directory of a Vista box.
Add this dll to the system32 directory of the wim file.

OR

you can install WAIK 2.1 this has named pipe integrated security connection on board by default.

Upgrade MDT

2008-03-29T14:32:00.002+01:00

Microsoft released recently a new version of MDT. This newer version is providing a better support for Vista SP1 and Server 2008 AND is solving some bugs of previous version
(like one is descirbed in the previous post).

If you don't want to loose your Boot images, Task Sequences and MDT packages you can upgrade MDT.

Check Michael Niehaus's blog, he gives a very nice overview of the different upgrade scenarios and
explains the best manner to do it.

http://blogs.technet.com/mniehaus/archive/2008/03.aspx

Not able to change MININT-xxx name with MDT-ZTI-SCCM

2008-03-17T08:09:00.002+01:00

Hi All,

If you want install PCs Zero Touch with MDT via SCCM and you notice in the ztigather.log that the PC is correctly gathering the correct value (machinename) out of the database but the value is not getting applied.

This in fact caused by bug into MDT, the reason is that that diskpart is choosing the first drive letter for the primary partition. The drive letter turns into E and the system cannot find the sysprep.inf. (in the postinstall phase this is file is supposed to get modified).

To solve this add following lines in zticonfigure.wsf starting from line 159.

ElseIf oFSO.FileExists("E:\sysprep\Sysprep.inf") then
sSysprepInf = "E:\sysprep\Sysprep.inf"oLogging.CreateEntry "Found Sysprep.inf at " & sSysprepInf & ".", LogTypeInfo

ADO connecton errors when trying to connect to MDT database

2008-03-10T08:14:00.001+01:00

Hi all,

If you have following error in ZTIGather please check out my post on Technet.

Error: Unable to create ADODB.Connection Object"

Technet: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2952634&SiteID=17

Coming up...

2008-01-30T13:49:00.000+01:00

Hello all,

I haven't got much time to publish new posts because I'm in the middle of the preparation of the upgrade scenario for SCCM and I'm also testing the new Microsoft Deployment to continue Zero Touch installations in an SCCM environment.

So keep on visiting this blog to discover my latest experiences regarding these topics!!

Nico

Unable to install and uninstall of SMS Client due to corrupt WMI

2007-12-19T07:42:00.000+01:00

Hi,

Recently I had an SMS client giving me following errors while I tried to install\uninstall SMS Client.

'unable to create namespace 80041002'
'2501 unable to delete WMI namespace CCM\SoftwareMeteringAgent 80041002'

WMIDiag learned me that my WMI was corrupt.

This script solved the issue:

execute following BAT files.

step1.bat
----------
cd /d %windir%\system32\wbem
for %i in (*.dll) do RegSvr32 -s %i
for %i in (*.exe) do %i /RegServer

net stop winmgmt /y

step2.bat
----------
cd c:\windows\system32\wbem

rd /S /Q repository

regsvr32 /s %systemroot%\system32\scecli.dll

regsvr32 /s %systemroot%\system32\userenv.dll

mofcomp cimwin32.mof

mofcomp cimwin32.mfl

mofcomp rsop.mof

mofcomp rsop.mfl

for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s

for /f %%s in ('dir /b *.mof') do mofcomp %%s

for /f %%s in ('dir /b *.mfl') do mofcomp %%s

mofcomp exwmi.mof

mofcomp -n:root\cimv2\applications\exchange wbemcons.mof

mofcomp -n:root\cimv2\applications\exchange smtpcons.mof

mofcomp exmgmt.mof

Enoy!

Problems with XP machines to connect to SMS console

2007-10-30T09:39:00.000+01:00

After upgrading to SMS 2003 SP3, I had problems with XP machines to connect to the SMS console. Also they could not add users in the local admin group with the error that enough
storage was available to execute the command.

This is the solution:

http://blogs.technet.com/askds/archive/2007/09/21/not-enough-storage-is-available-to-complete-this-operation.aspx

Reporting Point problems after upgrade to SMS 2003 SP3

2007-10-02T16:07:00.000+02:00

Error:

SMS Site Component Manager successfully used the SMS_SERVER_BOOTSTRAP_SERVER service to run the following program on site system "\\SERVER": E:\SMS\bin\i386\rpsetup.exe /install /siteserver:SERVERThe program failed for the following reason: Child process "E:\SMS\bin\i386\rpsetup.exe /install /siteserver:SERVER" took too long to execute, and the process (PID = 4484) was orphaned. Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system.Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system.SMS Site Component Manager cannot install component SMS_REPORTING_POINT until the program runs successfully. If this problem persists and you cannot fix it, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.

Solution:
- download the sysinternals streams tool- http://www.microsoft.com/technet/sysinternals/utilities/streams.mspx
- go to your SMS\Bin\i386 directory
- run 'streams reportinginstall.exe' if you see any streams registered for it, you can delete it with: - streams -d reportinginstall.exe

OSD with SCCM 2007

2007-09-15T20:28:00.001+02:00

Hello,

I created a nice document regarding OSD with SCCM 2007 based on the Microsoft TechNet pages.

If you are interested you can download it here:

http://www.myitforum.com/forums/m_164494/mpage_1/key_/tm.htm#164537

Enjoy - please add your comments...

Deploy Windows Vista in an SMS 2003 enviornment

2007-09-05T10:23:00.000+02:00

Hello,

Here you have my '10 steps-by-step' procedure to create a Vista image and to deploy this image via SMS 2003 OSD.

This procedure is tested and works fine.

Prerequisites.

On top of your existing SMS 2003 SPx enviornment with OSD_FP running do the following:

Install OSD_FP Update

Install BDD 2007

Install WAIK

SMS level: It’s possible to deploy Vista already with SMS SP1 or SP2, to manage the Vista machines in your environment your need SP3 or SCCM 2007 (SMSv4).

'10 steps-by-step' flow:

Create a Vista Reference machine manual or with LiteTouchPE_X86.iso.

This .iso is available in BDD.

(Execute 1 time)

On workbench.msc\Operating System node

Capture Winpe 2005 and Windows Server 2003 SP1

Create an OSD Capture CD via the SMS console and capture the Reference Machine.

Add the captured image (.wim version = 1.0 due to OSD_DP Update) to the Operating System node in workbench.msc.

Create build in workbench.msc (build node)

This is physically stored under \\ZTI$\

Create a Deployment Point in workbench.msc (Ex:SMS 2003 OSD)

Edit CS.ini and bootstrap.ini

Each time you change a setting you have to update your Deployment Point. Physically the Deployment Point is stored under ZTI$

(Execute 1 time)

Update WinPE2005 in SMS console with Generic_OSD_X86.iso

Create an Image Package in the SMS console (source: \\\OSD-

SRCPKG$.

Configure OSD program: all phases need to have ZeroTouchInstallion.vbs AND

all (*.*) under \\\ZTI$\

Update Distribution Points in SMS and Update System Package files

Create OSD Installation CD (tip: publish CD on WDS to download into RAMDISK of the PC)

10. Put PC that you want to install in SQL database or advertise it.

Have fun with it!! Please add your comments or questions!!

Nico (lnesta431)

Issues with SMS Administrator Console

2007-08-20T16:32:00.000+02:00

In my testlab I discovered some problems to install an SMS Administrator Console on a client PC.

After some troubleshooting I noticed I could not connect via WMI to my SMS Server.

Tough network, permissions, DCOM, WMI,... were all OK.

This patch solved the issue:

http://support.microsoft.com/kb/832521

August Patching

2007-08-17T11:48:00.000+02:00

Microsoft released these week new patches:

http://www.microsoft.com/technet/security/bulletin/ms07-aug.mspx

I'll deploy these with ITMU 3.0.

@ work - OSD Capture CD

2007-08-07T10:52:00.000+02:00

Hello all,

What a busy start after holiday ppff!!

I had to capture an image for 2 new hardware models (Lenovo laptops)

I could not use my previous caputure CD as (hell yeah) new SATA and NIC dirvers need to be added.

So let's start...

I noticed when I tried to capture that I could not access my C-drive, network was OK.

So I added my SATA strings into the txtsetup.sif and recreate a new capture CD.

When I re-tried to capture I could access my C-drive but suddenly I had no network anymore??

I compared with windiff and the only file that was changed was the txtsetup.sif...

Any idea why I suddenly lost my network? Nope! The drivers are on the CD for sure, but when I execute an ipconfig in labshell I get no reply.

Finally I receive the error 80040001, which is normal. (timeout)

After investigating everything inside out I re-created my .iso (oscdimg) and burned it again on CD, just the same like before...
and guess what it worked!!

I don't know why it didn't worked the first time, this proves again that IT sience is not really an exact sience!

My desk @ work

2007-07-12T15:58:00.001+02:00

Quite clean isn't it ;-)

Introduction

2007-07-12T15:47:00.000+02:00

Hello all,

Welcome to my blog! First of all I will introduce myself.

I'm 26 years old and I'm living in Aalst (Belgium).

Once I obtained my Bachelor degree in IT Science I started working in the IT Sector. (2001)
Since 4 years I'm working for one of the biggest motor companies in the world as SMS Administrator.

Next to the daily SMS admin tasks I was responsible for the implementation of BDD 2.5, OSD and ITMU.

On my blog you can find in the near future my latest findings, experience, tips&tricks,... regarding SMS 2003, SCCM 2007, OSD, BDD, ITMU,...

Some people will know me as lnesta431, this is my nickname on myitforum.com.

Hopefully this blog will be helpful and interesting for you!!

The good news for me is, that I'm leaving this weekend on holiday till the 31rst of July. So I hope as from the 1rst of August I'll post here from time to time.

Nico (lnesta431)