Finally a well deserved holiday
3 weeks west coast in the VS
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.
-
-
-
-
-
-
-
-
#
-
-
#
woensdag 23 juli 2008
Move of blog
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
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
vrijdag 6 juni 2008
Fatal error during upgrade to SCCM SP1
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
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
maandag 26 mei 2008
ZTI ERROR - Unhandled error returned by zticonfigure: Object required (424) and Unable to find CustomSettings.ini, rc = 1
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.
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.
dinsdag 20 mei 2008
zti error opening sql connection: cannot initialize sspi package
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.
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.
zaterdag 29 maart 2008
Upgrade MDT
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
(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
Abonneren op:
Posts (Atom)
