192.168.12.46\administrator 108C3876B246EF516490F3B2A17 I: <qt/>
*Lanndesk2*\OS Image Capture<qt/>
Is Lanndesk2 a typo? If not check that credentials to see if Administrator has access to the share. Also 192.168.12.46\administrator appears to be a local computer account.
This issue is almost identical to the "Waiting for command" issue seen with DOS imaging. In fact, all the troubleshooting is almost exactly the same (except of course that which is on the DOS side).
There is an article that discusses this:
About the only thing I have seen in WinPE that causes this that is different than that article is sometimes a miniscan comes in with the IP Address as all zeros, so the Core Server cannot know the IP and talk back to WinPE.
Run a Miniscan again from WinPE with this command:
miniscan.exe /usemacasname /nodeviceid
"GF-IT-1","ERR_Fail",-1917190197,0:02:13,1/24/2008 1:01:33 PM,1/24/2008 1:03:46 PM,"drvmap.exe 192.168.12.46\administrator 108C3876B246EF516490F3B2A17 I: <qt/>
Lanndesk2\OS Image Capture<qt/>, STATUS FACILITY=3513"
192.168.12.46 should be a domain name. You are using domain credentials to map a drive to a server share with this command so you need it to be domain\account_name
Wow, I was way off...I read the "capture does not start" as the script does not start.
Go with what bnelson says. That is likely the problem.
It should be Domain\Username for a domain user and ServerName\Username for a local user to the server.
The administrator account is a local admin account on the Landesk core server.
I havent added the server to domain.
Shud I make it a member of domain??????
I would add it to the domain (many more reasons than LANDesk reasons). I would also use a domain name for authentication to the share.
Also is the server name Lanndesk2?
In short, yes you should add it to the domain. The reasons, as ZMan said, extend beyond LANDesk. For this exercise it is not required that the server be joined to the domain however. You will need the server name in place of the server IP though.
Hey u spotted it ,,,,,
I was also wondering from where is it taking this name LANNdesk,
It was picking this from the host file entry on the server.
I removed it and it worked.
But now while deploying it is again haulting at the same spot,,,,,,after I select the deploy script it stucks there.
I initiated imagew.exe manually and validated the image by browsing it ,it failed
Can the image file be corrupted or not prperly imaged??????????