Setup failed applying image when using deployment services

Discussion:

(too old to reply)

Andreas Wöckl

2008-11-18 20:43:11 UTC

Hi group!

After doing a lot of investigations to find out why appying a custom image
fails I recogniced a problem with the Deployment Services.

My Szenario:

- Deployment Server: Windows 2008 english, 64 Bit, MDT 2008 Update 1
english, Waik 64 Bit
- Client: VM Virtual Machine, 32 Bit
- DHCP in the network: Windows Server 2003 German, 32 Bit

When using deployment services I get the following log (LtiApply.log)

______________
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.
For task sequence failures, please consult this log. LTIApply 18.11.2008
08:54:05 0 (0x0000)
Property DestinationLogicalDrive is now = C: LTIApply 18.11.2008 08:54:05 0
(0x0000)
------ Applying Windows image using Setup.exe ------ LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer to directory: C:\MININT\Operating Systems\WinVista
LTIApply 18.11.2008 08:54:05 0 (0x0000)
About to run command: cmd.exe /c
""\\192.168.2.2\Distribution$\Tools\X86\wdsmcast.exe" /verbose
/transfer-file /server:192.168.2.2 /namespace:"Distribution$"
/SourceFile:"Operating Systems\WinVista\WinVista.wim"
/DestinationFile:"C:\MININT\Operating Systems\WinVista\WinVista.wim"
/Username:schule.kirchdorf\woeckl /password:"schule2007!" >
"C:\MININT\SMSOSD\OSDLOGS\LTIApply_wdsmcast.log"" LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer could not be completed, rc = -2147024231, falling back to
using \\192.168.2.2\Distribution$\Operating Systems\WinVista\WinVista.wim
LTIApply 18.11.2008 09:04:57 0 (0x0000)
LTI applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim using SETUP.EXE LTIApply 18.11.2008 09:04:57 0
(0x0000)
Updating unattend.xml to change Setup UI Language from de-AT to de-DE
LTIApply 18.11.2008 09:04:57 0 (0x0000)
Cleaning off old operating system LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\Drivers LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\MININT LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\_SMSTaskSequence LTIApply 18.11.2008 09:04:57 0 (0x0000)
Installing image from \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim using command:
"\\192.168.2.2\Distribution$\Operating Systems\WinVista\Sources\setup.exe"
/noreboot /unattend:C:\MININT\unattend.xml
/m:"\\192.168.2.2\Distribution$\$OEM$" LTIApply 18.11.2008 09:04:57 0
(0x0000)
About to run command: "\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe" /noreboot
/unattend:C:\MININT\unattend.xml /m:"\\192.168.2.2\Distribution$\$OEM$"
LTIApply 18.11.2008 09:04:57 0 (0x0000)
ZTI Heartbeat: command has been running for 6 minutes (process ID 828)
LTIApply 18.11.2008 09:10:00 0 (0x0000)
ZTI Heartbeat: command has been running for 12 minutes (process ID 828)
LTIApply 18.11.2008 09:16:00 0 (0x0000)
ZTI Heartbeat: command has been running for 18 minutes (process ID 828)
LTIApply 18.11.2008 09:22:00 0 (0x0000)
ZTI Heartbeat: command has been running for 24 minutes (process ID 828)
LTIApply 18.11.2008 09:28:00 0 (0x0000)
Return code from command = 31 LTIApply 18.11.2008 09:33:07 0 (0x0000)
Setup failed applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim, rc = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
LTIApply COMPLETED. Return Value = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
ZTI ERROR - Non-zero return code by LTIApply, rc = 31 LTIApply 18.11.2008
09:33:07 0 (0x0000)
_________________

When stopping the deployment services and booting from CD it works - of
course without any multicast. The strange thing is that during PXE boot the
client machine always detects a 64 bit architecture although I am booting an
32 bit environment..?

Any ideas which actions to take - deployment without Multicast will be very
boring :)

Kind regards

Andy

unknown

2008-11-19 08:46:11 UTC

Permalink

Are you using WAIK 1.1? Is your WDS server running windows server
2008?

If tha hardware is capable of 32/64 bit, it will most times present
itself as a 64 bit machine. Hiwever, it will run the 32-bit boot image
just fine...

Sidebar... you should reset the password for your own user account
(schule.kirchdorf\woeck)... it is in clear text in the log file you
posted...

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by Andreas WÃ¶ckl
Hi group!
After doing a lot of investigations to find out why appying a custom image
fails I recogniced a problem with the Deployment Services.
- Deployment Server: Windows 2008 english, 64 Bit, MDT 2008 Update 1
english, Waik 64 Bit
- Client: VM Virtual Machine, 32 Bit
- DHCP in the network: Windows Server 2003 German, 32 Bit
When using deployment services I get the following log (LtiApply.log)
______________
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.
For task sequence failures, please consult this log. LTIApply 18.11.2008
08:54:05 0 (0x0000)
Property DestinationLogicalDrive is now = C: LTIApply 18.11.2008 08:54:05 0
(0x0000)
------ Applying Windows image using Setup.exe ------ LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer to directory: C:\MININT\Operating Systems\WinVista
LTIApply 18.11.2008 08:54:05 0 (0x0000)
About to run command: cmd.exe /c
""\\192.168.2.2\Distribution$\Tools\X86\wdsmcast.exe" /verbose
/transfer-file /server:192.168.2.2 /namespace:"Distribution$"
/SourceFile:"Operating Systems\WinVista\WinVista.wim"
/DestinationFile:"C:\MININT\Operating Systems\WinVista\WinVista.wim"
/Username:schule.kirchdorf\woeckl /password:"schule2007!" >
"C:\MININT\SMSOSD\OSDLOGS\LTIApply_wdsmcast.log"" LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer could not be completed, rc = -2147024231, falling back to
using \\192.168.2.2\Distribution$\Operating Systems\WinVista\WinVista.wim
LTIApply 18.11.2008 09:04:57 0 (0x0000)
LTI applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim using SETUP.EXE LTIApply 18.11.2008 09:04:57 0
(0x0000)
Updating unattend.xml to change Setup UI Language from de-AT to de-DE
LTIApply 18.11.2008 09:04:57 0 (0x0000)
Cleaning off old operating system LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\Drivers LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\MININT LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\_SMSTaskSequence LTIApply 18.11.2008 09:04:57 0 (0x0000)
Installing image from \\192.168.2.2\Distribution$\Operating
"\\192.168.2.2\Distribution$\Operating Systems\WinVista\Sources\setup.exe"
/noreboot /unattend:C:\MININT\unattend.xml
/m:"\\192.168.2.2\Distribution$\$OEM$" LTIApply 18.11.2008 09:04:57 0
(0x0000)
About to run command: "\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe" /noreboot
/unattend:C:\MININT\unattend.xml /m:"\\192.168.2.2\Distribution$\$OEM$"
LTIApply 18.11.2008 09:04:57 0 (0x0000)
ZTI Heartbeat: command has been running for 6 minutes (process ID 828)
LTIApply 18.11.2008 09:10:00 0 (0x0000)
ZTI Heartbeat: command has been running for 12 minutes (process ID 828)
LTIApply 18.11.2008 09:16:00 0 (0x0000)
ZTI Heartbeat: command has been running for 18 minutes (process ID 828)
LTIApply 18.11.2008 09:22:00 0 (0x0000)
ZTI Heartbeat: command has been running for 24 minutes (process ID 828)
LTIApply 18.11.2008 09:28:00 0 (0x0000)
Return code from command = 31 LTIApply 18.11.2008 09:33:07 0 (0x0000)
Setup failed applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim, rc = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
LTIApply COMPLETED. Return Value = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
ZTI ERROR - Non-zero return code by LTIApply, rc = 31 LTIApply 18.11.2008
09:33:07 0 (0x0000)
_________________
When stopping the deployment services and booting from CD it works - of
course without any multicast. The strange thing is that during PXE boot the
client machine always detects a 64 bit architecture although I am booting an
32 bit environment..?
Any ideas which actions to take - deployment without Multicast will be very
boring :)
Kind regards
Andy

Andreas Wöckl

2008-11-20 21:58:02 UTC

Permalink

Hi Johan!

@Password - thanks - I have recognized this a bit too late :(

@WDS: It is a 64 Bit system - it recognizes as a 64 bit system but I have
set the 32 bit boot image for 64 bit architectures in WDS :)

@WAIK - no I am using WAIK 1.0 - could this be the reason?

Kind regards

Andy

Post by unknown
Are you using WAIK 1.1? Is your WDS server running windows server
2008?
If tha hardware is capable of 32/64 bit, it will most times present
itself as a 64 bit machine. Hiwever, it will run the 32-bit boot image
just fine...
Sidebar... you should reset the password for your own user account
(schule.kirchdorf\woeck)... it is in clear text in the log file you
posted...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

unknown

2008-11-20 23:52:44 UTC

Permalink

Yes, you need WAIK 1.1 for multicast support...

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by Andreas WÃ¶ckl
Hi Johan!
@Password - thanks - I have recognized this a bit too late :(
@WDS: It is a 64 Bit system - it recognizes as a 64 bit system but I have
set the 32 bit boot image for 64 bit architectures in WDS :)
@WAIK - no I am using WAIK 1.0 - could this be the reason?
Kind regards
Andy

Andreas Wöckl

2008-11-21 06:38:00 UTC

Permalink

Hi Johan!

I am getting crazy - the component toolbox only gives the opportunity to
download 1.0 :(

Is the replacment only an "uninstall" and "Reinstall" of the WAIK or do I
have to look for further suprises :)

Thanks for your help!

Andy

Post by unknown
Yes, you need WAIK 1.1 for multicast support...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by Andreas WÃ¶ckl
Hi group!
After doing a lot of investigations to find out why appying a custom image
fails I recogniced a problem with the Deployment Services.
- Deployment Server: Windows 2008 english, 64 Bit, MDT 2008 Update 1
english, Waik 64 Bit
- Client: VM Virtual Machine, 32 Bit
- DHCP in the network: Windows Server 2003 German, 32 Bit
When using deployment services I get the following log (LtiApply.log)
______________
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.
For task sequence failures, please consult this log. LTIApply 18.11.2008
08:54:05 0 (0x0000)
Property DestinationLogicalDrive is now = C: LTIApply 18.11.2008
08:54:05
0
(0x0000)
------ Applying Windows image using Setup.exe ------ LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer to directory: C:\MININT\Operating Systems\WinVista
LTIApply 18.11.2008 08:54:05 0 (0x0000)
About to run command: cmd.exe /c
""\\192.168.2.2\Distribution$\Tools\X86\wdsmcast.exe" /verbose
/transfer-file /server:192.168.2.2 /namespace:"Distribution$"
/SourceFile:"Operating Systems\WinVista\WinVista.wim"
/DestinationFile:"C:\MININT\Operating Systems\WinVista\WinVista.wim"
/Username:schule.kirchdorf\woeckl /password:"schule2007!" >
"C:\MININT\SMSOSD\OSDLOGS\LTIApply_wdsmcast.log"" LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer could not be completed, rc = -2147024231, falling
back
to
using \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim
LTIApply 18.11.2008 09:04:57 0 (0x0000)
LTI applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim using SETUP.EXE LTIApply 18.11.2008
09:04:57
0
(0x0000)
Updating unattend.xml to change Setup UI Language from de-AT to de-DE
LTIApply 18.11.2008 09:04:57 0 (0x0000)
Cleaning off old operating system LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\Drivers LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\MININT LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\_SMSTaskSequence LTIApply 18.11.2008 09:04:57 0 (0x0000)
Installing image from \\192.168.2.2\Distribution$\Operating
"\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe"
/noreboot /unattend:C:\MININT\unattend.xml
/m:"\\192.168.2.2\Distribution$\$OEM$" LTIApply 18.11.2008 09:04:57 0
(0x0000)
About to run command: "\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe" /noreboot
/unattend:C:\MININT\unattend.xml /m:"\\192.168.2.2\Distribution$\$OEM$"
LTIApply 18.11.2008 09:04:57 0 (0x0000)
ZTI Heartbeat: command has been running for 6 minutes (process ID 828)
LTIApply 18.11.2008 09:10:00 0 (0x0000)
ZTI Heartbeat: command has been running for 12 minutes (process ID 828)
LTIApply 18.11.2008 09:16:00 0 (0x0000)
ZTI Heartbeat: command has been running for 18 minutes (process ID 828)
LTIApply 18.11.2008 09:22:00 0 (0x0000)
ZTI Heartbeat: command has been running for 24 minutes (process ID 828)
LTIApply 18.11.2008 09:28:00 0 (0x0000)
Return code from command = 31 LTIApply 18.11.2008 09:33:07 0 (0x0000)
Setup failed applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim, rc = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
LTIApply COMPLETED. Return Value = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
ZTI ERROR - Non-zero return code by LTIApply, rc = 31 LTIApply 18.11.2008
09:33:07 0 (0x0000)
_________________
When stopping the deployment services and booting from CD it works - of
course without any multicast. The strange thing is that during PXE boot the
client machine always detects a 64 bit architecture although I am
booting
an
32 bit environment..?
Any ideas which actions to take - deployment without Multicast will be very
boring :)
Kind regards
Andy

Andreas Wöckl

2008-11-21 06:41:47 UTC

Permalink

Hi Johan!

Just another question - I also found some hints that "IGMP Snooping" has to
be activated at the switch - is this correct?

Kind regards

Andy

Post by unknown
Yes, you need WAIK 1.1 for multicast support...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by Andreas WÃ¶ckl
Hi group!
After doing a lot of investigations to find out why appying a custom image
fails I recogniced a problem with the Deployment Services.
- Deployment Server: Windows 2008 english, 64 Bit, MDT 2008 Update 1
english, Waik 64 Bit
- Client: VM Virtual Machine, 32 Bit
- DHCP in the network: Windows Server 2003 German, 32 Bit
When using deployment services I get the following log (LtiApply.log)
______________
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.
For task sequence failures, please consult this log. LTIApply 18.11.2008
08:54:05 0 (0x0000)
Property DestinationLogicalDrive is now = C: LTIApply 18.11.2008
08:54:05
0
(0x0000)
------ Applying Windows image using Setup.exe ------ LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer to directory: C:\MININT\Operating Systems\WinVista
LTIApply 18.11.2008 08:54:05 0 (0x0000)
About to run command: cmd.exe /c
""\\192.168.2.2\Distribution$\Tools\X86\wdsmcast.exe" /verbose
/transfer-file /server:192.168.2.2 /namespace:"Distribution$"
/SourceFile:"Operating Systems\WinVista\WinVista.wim"
/DestinationFile:"C:\MININT\Operating Systems\WinVista\WinVista.wim"
/Username:schule.kirchdorf\woeckl /password:"schule2007!" >
"C:\MININT\SMSOSD\OSDLOGS\LTIApply_wdsmcast.log"" LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer could not be completed, rc = -2147024231, falling
back
to
using \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim
LTIApply 18.11.2008 09:04:57 0 (0x0000)
LTI applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim using SETUP.EXE LTIApply 18.11.2008
09:04:57
0
(0x0000)
Updating unattend.xml to change Setup UI Language from de-AT to de-DE
LTIApply 18.11.2008 09:04:57 0 (0x0000)
Cleaning off old operating system LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\Drivers LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\MININT LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\_SMSTaskSequence LTIApply 18.11.2008 09:04:57 0 (0x0000)
Installing image from \\192.168.2.2\Distribution$\Operating
"\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe"
/noreboot /unattend:C:\MININT\unattend.xml
/m:"\\192.168.2.2\Distribution$\$OEM$" LTIApply 18.11.2008 09:04:57 0
(0x0000)
About to run command: "\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe" /noreboot
/unattend:C:\MININT\unattend.xml /m:"\\192.168.2.2\Distribution$\$OEM$"
LTIApply 18.11.2008 09:04:57 0 (0x0000)
ZTI Heartbeat: command has been running for 6 minutes (process ID 828)
LTIApply 18.11.2008 09:10:00 0 (0x0000)
ZTI Heartbeat: command has been running for 12 minutes (process ID 828)
LTIApply 18.11.2008 09:16:00 0 (0x0000)
ZTI Heartbeat: command has been running for 18 minutes (process ID 828)
LTIApply 18.11.2008 09:22:00 0 (0x0000)
ZTI Heartbeat: command has been running for 24 minutes (process ID 828)
LTIApply 18.11.2008 09:28:00 0 (0x0000)
Return code from command = 31 LTIApply 18.11.2008 09:33:07 0 (0x0000)
Setup failed applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim, rc = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
LTIApply COMPLETED. Return Value = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
ZTI ERROR - Non-zero return code by LTIApply, rc = 31 LTIApply 18.11.2008
09:33:07 0 (0x0000)
_________________
When stopping the deployment services and booting from CD it works - of
course without any multicast. The strange thing is that during PXE boot the
client machine always detects a 64 bit architecture although I am
booting
an
32 bit environment..?
Any ideas which actions to take - deployment without Multicast will be very
boring :)
Kind regards
Andy

unknown

2008-11-24 10:57:54 UTC

Permalink

Yes... :)

/ Johan

Post by Andreas WÃ¶ckl
Hi Johan!
Just another question - I also found some hints that "IGMP Snooping" has to
be activated at the switch - is this correct?
Kind regards
Andy

Post by unknown
Yes, you need WAIK 1.1 for multicast support...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by Andreas WÃ¶ckl
Hi group!
After doing a lot of investigations to find out why appying a custom image
fails I recogniced a problem with the Deployment Services.
- Deployment Server: Windows 2008 english, 64 Bit, MDT 2008 Update 1
english, Waik 64 Bit
- Client: VM Virtual Machine, 32 Bit
- DHCP in the network: Windows Server 2003 German, 32 Bit
When using deployment services I get the following log (LtiApply.log)
______________
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.
For task sequence failures, please consult this log. LTIApply 18.11.2008
08:54:05 0 (0x0000)
Property DestinationLogicalDrive is now = C: LTIApply 18.11.2008
08:54:05
0
(0x0000)
------ Applying Windows image using Setup.exe ------ LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer to directory: C:\MININT\Operating Systems\WinVista
LTIApply 18.11.2008 08:54:05 0 (0x0000)
About to run command: cmd.exe /c
""\\192.168.2.2\Distribution$\Tools\X86\wdsmcast.exe" /verbose
/transfer-file /server:192.168.2.2 /namespace:"Distribution$"
/SourceFile:"Operating Systems\WinVista\WinVista.wim"
/DestinationFile:"C:\MININT\Operating Systems\WinVista\WinVista.wim"
/Username:schule.kirchdorf\woeckl /password:"schule2007!" >
"C:\MININT\SMSOSD\OSDLOGS\LTIApply_wdsmcast.log"" LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer could not be completed, rc = -2147024231, falling
back
to
using \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim
LTIApply 18.11.2008 09:04:57 0 (0x0000)
LTI applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim using SETUP.EXE LTIApply 18.11.2008
09:04:57
0
(0x0000)
Updating unattend.xml to change Setup UI Language from de-AT to de-DE
LTIApply 18.11.2008 09:04:57 0 (0x0000)
Cleaning off old operating system LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\Drivers LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\MININT LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\_SMSTaskSequence LTIApply 18.11.2008 09:04:57 0 (0x0000)
Installing image from \\192.168.2.2\Distribution$\Operating
"\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe"
/noreboot /unattend:C:\MININT\unattend.xml
/m:"\\192.168.2.2\Distribution$\$OEM$" LTIApply 18.11.2008 09:04:57 0
(0x0000)
About to run command: "\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe" /noreboot
/unattend:C:\MININT\unattend.xml /m:"\\192.168.2.2\Distribution$\$OEM$"
LTIApply 18.11.2008 09:04:57 0 (0x0000)
ZTI Heartbeat: command has been running for 6 minutes (process ID 828)
LTIApply 18.11.2008 09:10:00 0 (0x0000)
ZTI Heartbeat: command has been running for 12 minutes (process ID 828)
LTIApply 18.11.2008 09:16:00 0 (0x0000)
ZTI Heartbeat: command has been running for 18 minutes (process ID 828)
LTIApply 18.11.2008 09:22:00 0 (0x0000)
ZTI Heartbeat: command has been running for 24 minutes (process ID 828)
LTIApply 18.11.2008 09:28:00 0 (0x0000)
Return code from command = 31 LTIApply 18.11.2008 09:33:07 0 (0x0000)
Setup failed applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim, rc = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
LTIApply COMPLETED. Return Value = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
ZTI ERROR - Non-zero return code by LTIApply, rc = 31 LTIApply 18.11.2008
09:33:07 0 (0x0000)
_________________
When stopping the deployment services and booting from CD it works - of
course without any multicast. The strange thing is that during PXE boot the
client machine always detects a 64 bit architecture although I am
booting
an
32 bit environment..?
Any ideas which actions to take - deployment without Multicast will be very
boring :)
Kind regards
Andy

Andreas Wöckl

2008-11-21 07:04:52 UTC

Permalink

Hi Johan!

Shame on me - better to take more time to investigate something but of
course WAIK 1.1 is installed - WAIK 1.0 is unavailable for download in the
component toolbox!

The amazing thing is that the Multicast Transfer comes up to at about 85 %
and then stops. With the core image there is no problem but with the
custom..

I trid with the original custom image (10 GB) and with a smaller custom
image (7 GB) - both have the same problems.

What I really can not understand is the fact that it work without multicast
when starting from CD?

Kind regards

Andy

Post by unknown
Yes, you need WAIK 1.1 for multicast support...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by Andreas WÃ¶ckl
Hi group!
After doing a lot of investigations to find out why appying a custom image
fails I recogniced a problem with the Deployment Services.
- Deployment Server: Windows 2008 english, 64 Bit, MDT 2008 Update 1
english, Waik 64 Bit
- Client: VM Virtual Machine, 32 Bit
- DHCP in the network: Windows Server 2003 German, 32 Bit
When using deployment services I get the following log (LtiApply.log)
______________
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.
For task sequence failures, please consult this log. LTIApply 18.11.2008
08:54:05 0 (0x0000)
Property DestinationLogicalDrive is now = C: LTIApply 18.11.2008
08:54:05
0
(0x0000)
------ Applying Windows image using Setup.exe ------ LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer to directory: C:\MININT\Operating Systems\WinVista
LTIApply 18.11.2008 08:54:05 0 (0x0000)
About to run command: cmd.exe /c
""\\192.168.2.2\Distribution$\Tools\X86\wdsmcast.exe" /verbose
/transfer-file /server:192.168.2.2 /namespace:"Distribution$"
/SourceFile:"Operating Systems\WinVista\WinVista.wim"
/DestinationFile:"C:\MININT\Operating Systems\WinVista\WinVista.wim"
/Username:schule.kirchdorf\woeckl /password:"schule2007!" >
"C:\MININT\SMSOSD\OSDLOGS\LTIApply_wdsmcast.log"" LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer could not be completed, rc = -2147024231, falling
back
to
using \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim
LTIApply 18.11.2008 09:04:57 0 (0x0000)
LTI applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim using SETUP.EXE LTIApply 18.11.2008
09:04:57
0
(0x0000)
Updating unattend.xml to change Setup UI Language from de-AT to de-DE
LTIApply 18.11.2008 09:04:57 0 (0x0000)
Cleaning off old operating system LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\Drivers LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\MININT LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\_SMSTaskSequence LTIApply 18.11.2008 09:04:57 0 (0x0000)
Installing image from \\192.168.2.2\Distribution$\Operating
"\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe"
/noreboot /unattend:C:\MININT\unattend.xml
/m:"\\192.168.2.2\Distribution$\$OEM$" LTIApply 18.11.2008 09:04:57 0
(0x0000)
About to run command: "\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe" /noreboot
/unattend:C:\MININT\unattend.xml /m:"\\192.168.2.2\Distribution$\$OEM$"
LTIApply 18.11.2008 09:04:57 0 (0x0000)
ZTI Heartbeat: command has been running for 6 minutes (process ID 828)
LTIApply 18.11.2008 09:10:00 0 (0x0000)
ZTI Heartbeat: command has been running for 12 minutes (process ID 828)
LTIApply 18.11.2008 09:16:00 0 (0x0000)
ZTI Heartbeat: command has been running for 18 minutes (process ID 828)
LTIApply 18.11.2008 09:22:00 0 (0x0000)
ZTI Heartbeat: command has been running for 24 minutes (process ID 828)
LTIApply 18.11.2008 09:28:00 0 (0x0000)
Return code from command = 31 LTIApply 18.11.2008 09:33:07 0 (0x0000)
Setup failed applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim, rc = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
LTIApply COMPLETED. Return Value = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
ZTI ERROR - Non-zero return code by LTIApply, rc = 31 LTIApply 18.11.2008
09:33:07 0 (0x0000)
_________________
When stopping the deployment services and booting from CD it works - of
course without any multicast. The strange thing is that during PXE boot the
client machine always detects a 64 bit architecture although I am
booting
an
32 bit environment..?
Any ideas which actions to take - deployment without Multicast will be very
boring :)
Kind regards
Andy

unknown

2008-11-24 11:03:06 UTC

Permalink

Well, multicast and unicast transfers are handled very differently...

Multicast issues can be quite challenging to trobleshoot, but if
you're lucky its as easy as updating the nic driver on the server...

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by Andreas WÃ¶ckl
Hi Johan!
Shame on me - better to take more time to investigate something but of
course WAIK 1.1 is installed - WAIK 1.0 is unavailable for download in the
component toolbox!
The amazing thing is that the Multicast Transfer comes up to at about 85 %
and then stops. With the core image there is no problem but with the
custom..
I trid with the original custom image (10 GB) and with a smaller custom
image (7 GB) - both have the same problems.
What I really can not understand is the fact that it work without multicast
when starting from CD?
Kind regards
Andy

Post by unknown
Yes, you need WAIK 1.1 for multicast support...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by Andreas WÃ¶ckl
Hi group!
After doing a lot of investigations to find out why appying a custom image
fails I recogniced a problem with the Deployment Services.
- Deployment Server: Windows 2008 english, 64 Bit, MDT 2008 Update 1
english, Waik 64 Bit
- Client: VM Virtual Machine, 32 Bit
- DHCP in the network: Windows Server 2003 German, 32 Bit
When using deployment services I get the following log (LtiApply.log)
______________
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.
For task sequence failures, please consult this log. LTIApply 18.11.2008
08:54:05 0 (0x0000)
Property DestinationLogicalDrive is now = C: LTIApply 18.11.2008
08:54:05
0
(0x0000)
------ Applying Windows image using Setup.exe ------ LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer to directory: C:\MININT\Operating Systems\WinVista
LTIApply 18.11.2008 08:54:05 0 (0x0000)
About to run command: cmd.exe /c
""\\192.168.2.2\Distribution$\Tools\X86\wdsmcast.exe" /verbose
/transfer-file /server:192.168.2.2 /namespace:"Distribution$"
/SourceFile:"Operating Systems\WinVista\WinVista.wim"
/DestinationFile:"C:\MININT\Operating Systems\WinVista\WinVista.wim"
/Username:schule.kirchdorf\woeckl /password:"schule2007!" >
"C:\MININT\SMSOSD\OSDLOGS\LTIApply_wdsmcast.log"" LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer could not be completed, rc = -2147024231, falling
back
to
using \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim
LTIApply 18.11.2008 09:04:57 0 (0x0000)
LTI applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim using SETUP.EXE LTIApply 18.11.2008
09:04:57
0
(0x0000)
Updating unattend.xml to change Setup UI Language from de-AT to de-DE
LTIApply 18.11.2008 09:04:57 0 (0x0000)
Cleaning off old operating system LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\Drivers LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\MININT LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\_SMSTaskSequence LTIApply 18.11.2008 09:04:57 0 (0x0000)
Installing image from \\192.168.2.2\Distribution$\Operating
"\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe"
/noreboot /unattend:C:\MININT\unattend.xml
/m:"\\192.168.2.2\Distribution$\$OEM$" LTIApply 18.11.2008 09:04:57 0
(0x0000)
About to run command: "\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe" /noreboot
/unattend:C:\MININT\unattend.xml /m:"\\192.168.2.2\Distribution$\$OEM$"
LTIApply 18.11.2008 09:04:57 0 (0x0000)
ZTI Heartbeat: command has been running for 6 minutes (process ID 828)
LTIApply 18.11.2008 09:10:00 0 (0x0000)
ZTI Heartbeat: command has been running for 12 minutes (process ID 828)
LTIApply 18.11.2008 09:16:00 0 (0x0000)
ZTI Heartbeat: command has been running for 18 minutes (process ID 828)
LTIApply 18.11.2008 09:22:00 0 (0x0000)
ZTI Heartbeat: command has been running for 24 minutes (process ID 828)
LTIApply 18.11.2008 09:28:00 0 (0x0000)
Return code from command = 31 LTIApply 18.11.2008 09:33:07 0 (0x0000)
Setup failed applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim, rc = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
LTIApply COMPLETED. Return Value = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
ZTI ERROR - Non-zero return code by LTIApply, rc = 31 LTIApply 18.11.2008
09:33:07 0 (0x0000)
_________________
When stopping the deployment services and booting from CD it works - of
course without any multicast. The strange thing is that during PXE boot the
client machine always detects a 64 bit architecture although I am
booting
an
32 bit environment..?
Any ideas which actions to take - deployment without Multicast will be very
boring :)
Kind regards
Andy

Andreas Wöckl

2008-11-25 19:32:02 UTC

Permalink

Hi Johan!

Hmm - I willl have to check the driver issue!

My problem is that the multicast transfer starts - but it stops at about 80
to 85 % - even if the image is 3 GB smaller. Could this really be a driver
issue?

Do you have any ideas how to troubleshoot this issue?

Kind regards

Andy

Post by unknown
Well, multicast and unicast transfers are handled very differently...
Multicast issues can be quite challenging to trobleshoot, but if
you're lucky its as easy as updating the nic driver on the server...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by unknown
Yes, you need WAIK 1.1 for multicast support...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by Andreas WÃ¶ckl
Hi group!
After doing a lot of investigations to find out why appying a custom image
fails I recogniced a problem with the Deployment Services.
- Deployment Server: Windows 2008 english, 64 Bit, MDT 2008 Update 1
english, Waik 64 Bit
- Client: VM Virtual Machine, 32 Bit
- DHCP in the network: Windows Server 2003 German, 32 Bit
When using deployment services I get the following log (LtiApply.log)
______________
The task sequencer log is located at
X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.
For task sequence failures, please consult this log. LTIApply 18.11.2008
08:54:05 0 (0x0000)
Property DestinationLogicalDrive is now = C: LTIApply 18.11.2008
08:54:05
0
(0x0000)
------ Applying Windows image using Setup.exe ------ LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer to directory: C:\MININT\Operating Systems\WinVista
LTIApply 18.11.2008 08:54:05 0 (0x0000)
About to run command: cmd.exe /c
""\\192.168.2.2\Distribution$\Tools\X86\wdsmcast.exe" /verbose
/transfer-file /server:192.168.2.2 /namespace:"Distribution$"
/SourceFile:"Operating Systems\WinVista\WinVista.wim"
/DestinationFile:"C:\MININT\Operating Systems\WinVista\WinVista.wim"
/Username:schule.kirchdorf\woeckl /password:"schule2007!" >
"C:\MININT\SMSOSD\OSDLOGS\LTIApply_wdsmcast.log"" LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer could not be completed, rc = -2147024231, falling
back
to
using \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim
LTIApply 18.11.2008 09:04:57 0 (0x0000)
LTI applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim using SETUP.EXE LTIApply 18.11.2008
09:04:57
0
(0x0000)
Updating unattend.xml to change Setup UI Language from de-AT to de-DE
LTIApply 18.11.2008 09:04:57 0 (0x0000)
Cleaning off old operating system LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\Drivers LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\MININT LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\_SMSTaskSequence LTIApply 18.11.2008 09:04:57 0 (0x0000)
Installing image from \\192.168.2.2\Distribution$\Operating
"\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe"
/noreboot /unattend:C:\MININT\unattend.xml
/m:"\\192.168.2.2\Distribution$\$OEM$" LTIApply 18.11.2008 09:04:57 0
(0x0000)
About to run command: "\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe" /noreboot
/unattend:C:\MININT\unattend.xml
/m:"\\192.168.2.2\Distribution$\$OEM$"
LTIApply 18.11.2008 09:04:57 0 (0x0000)
ZTI Heartbeat: command has been running for 6 minutes (process ID 828)
LTIApply 18.11.2008 09:10:00 0 (0x0000)
ZTI Heartbeat: command has been running for 12 minutes (process ID 828)
LTIApply 18.11.2008 09:16:00 0 (0x0000)
ZTI Heartbeat: command has been running for 18 minutes (process ID 828)
LTIApply 18.11.2008 09:22:00 0 (0x0000)
ZTI Heartbeat: command has been running for 24 minutes (process ID 828)
LTIApply 18.11.2008 09:28:00 0 (0x0000)
Return code from command = 31 LTIApply 18.11.2008 09:33:07 0 (0x0000)
Setup failed applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim, rc = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
LTIApply COMPLETED. Return Value = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
ZTI ERROR - Non-zero return code by LTIApply, rc = 31 LTIApply 18.11.2008
09:33:07 0 (0x0000)
_________________
When stopping the deployment services and booting from CD it works - of
course without any multicast. The strange thing is that during PXE
boot
the
client machine always detects a 64 bit architecture although I am
booting
an
32 bit environment..?
Any ideas which actions to take - deployment without Multicast will be very
boring :)
Kind regards
Andy

unknown

2008-11-25 22:50:49 UTC

Permalink

Is it always the same client that fails? Do you see any related
error in the setupact.log file on the client?

Some multicast troubleshooting steps...

Try different Network Profiles on the Network Settings tab, and see if
it behaves differently...

Check the multicast performance counters on the WDS server and see if
you have any package loss on the network

Enable multicast tracing on the WDS Server.

Replace the switch.

Sniff the network.

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by Andreas WÃ¶ckl
Hi Johan!
Hmm - I willl have to check the driver issue!
My problem is that the multicast transfer starts - but it stops at about 80
to 85 % - even if the image is 3 GB smaller. Could this really be a driver
issue?
Do you have any ideas how to troubleshoot this issue?
Kind regards
Andy

Post by unknown
Yes, you need WAIK 1.1 for multicast support...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by Andreas WÃ¶ckl
Hi group!
After doing a lot of investigations to find out why appying a custom image
fails I recogniced a problem with the Deployment Services.
- Deployment Server: Windows 2008 english, 64 Bit, MDT 2008 Update 1
english, Waik 64 Bit
- Client: VM Virtual Machine, 32 Bit
- DHCP in the network: Windows Server 2003 German, 32 Bit
When using deployment services I get the following log (LtiApply.log)
______________
The task sequencer log is located at
X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.
For task sequence failures, please consult this log. LTIApply 18.11.2008
08:54:05 0 (0x0000)
Property DestinationLogicalDrive is now = C: LTIApply 18.11.2008
08:54:05
0
(0x0000)
------ Applying Windows image using Setup.exe ------ LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer to directory: C:\MININT\Operating Systems\WinVista
LTIApply 18.11.2008 08:54:05 0 (0x0000)
About to run command: cmd.exe /c
""\\192.168.2.2\Distribution$\Tools\X86\wdsmcast.exe" /verbose
/transfer-file /server:192.168.2.2 /namespace:"Distribution$"
/SourceFile:"Operating Systems\WinVista\WinVista.wim"
/DestinationFile:"C:\MININT\Operating Systems\WinVista\WinVista.wim"
/Username:schule.kirchdorf\woeckl /password:"schule2007!" >
"C:\MININT\SMSOSD\OSDLOGS\LTIApply_wdsmcast.log"" LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer could not be completed, rc = -2147024231, falling
back
to
using \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim
LTIApply 18.11.2008 09:04:57 0 (0x0000)
LTI applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim using SETUP.EXE LTIApply 18.11.2008
09:04:57
0
(0x0000)
Updating unattend.xml to change Setup UI Language from de-AT to de-DE
LTIApply 18.11.2008 09:04:57 0 (0x0000)
Cleaning off old operating system LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\Drivers LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\MININT LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\_SMSTaskSequence LTIApply 18.11.2008 09:04:57 0 (0x0000)
Installing image from \\192.168.2.2\Distribution$\Operating
"\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe"
/noreboot /unattend:C:\MININT\unattend.xml
/m:"\\192.168.2.2\Distribution$\$OEM$" LTIApply 18.11.2008 09:04:57 0
(0x0000)
About to run command: "\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe" /noreboot
/unattend:C:\MININT\unattend.xml
/m:"\\192.168.2.2\Distribution$\$OEM$"
LTIApply 18.11.2008 09:04:57 0 (0x0000)
ZTI Heartbeat: command has been running for 6 minutes (process ID 828)
LTIApply 18.11.2008 09:10:00 0 (0x0000)
ZTI Heartbeat: command has been running for 12 minutes (process ID 828)
LTIApply 18.11.2008 09:16:00 0 (0x0000)
ZTI Heartbeat: command has been running for 18 minutes (process ID 828)
LTIApply 18.11.2008 09:22:00 0 (0x0000)
ZTI Heartbeat: command has been running for 24 minutes (process ID 828)
LTIApply 18.11.2008 09:28:00 0 (0x0000)
Return code from command = 31 LTIApply 18.11.2008 09:33:07 0 (0x0000)
Setup failed applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim, rc = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
LTIApply COMPLETED. Return Value = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
ZTI ERROR - Non-zero return code by LTIApply, rc = 31 LTIApply 18.11.2008
09:33:07 0 (0x0000)
_________________
When stopping the deployment services and booting from CD it works - of
course without any multicast. The strange thing is that during PXE
boot
the
client machine always detects a 64 bit architecture although I am
booting
an
32 bit environment..?
Any ideas which actions to take - deployment without Multicast will be very
boring :)
Kind regards
Andy

Andreas Wöckl

2008-11-28 08:39:56 UTC

Permalink

HI Johan!

Thanks - I will try now with a seperate switch - yesterday it worked for 3
times - and did not work for 2 time.. :)

Quite tricky..

Kind regards

Andy

Post by unknown
Is it always the same client that fails? Do you see any related
error in the setupact.log file on the client?
Some multicast troubleshooting steps...
Try different Network Profiles on the Network Settings tab, and see if
it behaves differently...
Check the multicast performance counters on the WDS server and see if
you have any package loss on the network
Enable multicast tracing on the WDS Server.
Replace the switch.
Sniff the network.
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by unknown
Yes, you need WAIK 1.1 for multicast support...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by Andreas WÃ¶ckl
Hi group!
After doing a lot of investigations to find out why appying a custom image
fails I recogniced a problem with the Deployment Services.
- Deployment Server: Windows 2008 english, 64 Bit, MDT 2008 Update 1
english, Waik 64 Bit
- Client: VM Virtual Machine, 32 Bit
- DHCP in the network: Windows Server 2003 German, 32 Bit
When using deployment services I get the following log
(LtiApply.log)
______________
The task sequencer log is located at
X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.
For task sequence failures, please consult this log. LTIApply 18.11.2008
08:54:05 0 (0x0000)
Property DestinationLogicalDrive is now = C: LTIApply 18.11.2008
08:54:05
0
(0x0000)
------ Applying Windows image using Setup.exe ------ LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer to directory: C:\MININT\Operating
Systems\WinVista
LTIApply 18.11.2008 08:54:05 0 (0x0000)
About to run command: cmd.exe /c
""\\192.168.2.2\Distribution$\Tools\X86\wdsmcast.exe" /verbose
/transfer-file /server:192.168.2.2 /namespace:"Distribution$"
/SourceFile:"Operating Systems\WinVista\WinVista.wim"
/DestinationFile:"C:\MININT\Operating Systems\WinVista\WinVista.wim"
/Username:schule.kirchdorf\woeckl /password:"schule2007!" >
"C:\MININT\SMSOSD\OSDLOGS\LTIApply_wdsmcast.log"" LTIApply 18.11.2008
08:54:05 0 (0x0000)
Multicast transfer could not be completed, rc = -2147024231, falling
back
to
using \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim
LTIApply 18.11.2008 09:04:57 0 (0x0000)
LTI applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim using SETUP.EXE LTIApply 18.11.2008
09:04:57
0
(0x0000)
Updating unattend.xml to change Setup UI Language from de-AT to de-DE
LTIApply 18.11.2008 09:04:57 0 (0x0000)
Cleaning off old operating system LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\Drivers LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\MININT LTIApply 18.11.2008 09:04:57 0 (0x0000)
Skipping C:\_SMSTaskSequence LTIApply 18.11.2008 09:04:57 0 (0x0000)
Installing image from \\192.168.2.2\Distribution$\Operating
"\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe"
/noreboot /unattend:C:\MININT\unattend.xml
/m:"\\192.168.2.2\Distribution$\$OEM$" LTIApply 18.11.2008 09:04:57 0
(0x0000)
About to run command: "\\192.168.2.2\Distribution$\Operating
Systems\WinVista\Sources\setup.exe" /noreboot
/unattend:C:\MININT\unattend.xml
/m:"\\192.168.2.2\Distribution$\$OEM$"
LTIApply 18.11.2008 09:04:57 0 (0x0000)
ZTI Heartbeat: command has been running for 6 minutes (process ID 828)
LTIApply 18.11.2008 09:10:00 0 (0x0000)
ZTI Heartbeat: command has been running for 12 minutes (process ID 828)
LTIApply 18.11.2008 09:16:00 0 (0x0000)
ZTI Heartbeat: command has been running for 18 minutes (process ID 828)
LTIApply 18.11.2008 09:22:00 0 (0x0000)
ZTI Heartbeat: command has been running for 24 minutes (process ID 828)
LTIApply 18.11.2008 09:28:00 0 (0x0000)
Return code from command = 31 LTIApply 18.11.2008 09:33:07 0 (0x0000)
Setup failed applying image \\192.168.2.2\Distribution$\Operating
Systems\WinVista\WinVista.wim, rc = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
LTIApply COMPLETED. Return Value = 31 LTIApply 18.11.2008 09:33:07 0
(0x0000)
ZTI ERROR - Non-zero return code by LTIApply, rc = 31 LTIApply 18.11.2008
09:33:07 0 (0x0000)
_________________
When stopping the deployment services and booting from CD it works - of
course without any multicast. The strange thing is that during PXE
boot
the
client machine always detects a 64 bit architecture although I am
booting
an
32 bit environment..?
Any ideas which actions to take - deployment without Multicast will
be
very
boring :)
Kind regards
Andy