Deployment Solution

Hi i use winPE for pxe boot and it halt on following

hope someone has a solution


Please wait while Altiris Windows PE2 x86 (PXE boot) loads...

Initializing Windows PE2...
Loading registry settings...
Loading reg2000.reg...
Initializing network...
Starting the network...
Loading drivers...
Using Dynamic IP.
Configuring WinPE firewall...
Firewall disabled.
Establishing network connection...
Validating IP address...
Restarting DHCP client service: retry 1...
Authenticating connection...
Could not authenticate network connection.
Mapping network drives...
System error 53 has occurred.

The network path was not found.

The command completed successfully.

Deployment share mapped to F:

Starting Agent...
Locating Agent...
Searching Deployment Share for Agent...
Unable to locate remote agent "altiris-aclient-*.x86.exe" on Deployment Share.

Starting Local Agent X:\aclient.exe...
Unable to find agent "X:\aclient.exe".

Calling custom actions...

Startup complete.

X:\>dir

I suspect that either your credentials are wrong (can't map the drive) or the drive letter F: is already in use. Are you trying to image a server?

Hi thanks for your quick answer
Im having it just for clients so no servers
and as you can see in the log window i get the f: mapped but it cant find the aclient files?
i can find them if i browse the location
any other suggestion?

best regards Johan

System Error 53 is a Microsoft message, basically telling you the share name can't be reached. There are many reasons to this, primarily file and printer sharing not being enabled, or a firewall is in-between.

Do you map more drives in your script than just the express (F: by default)?

What i did is used a local account not AD account. It seems to like that better.

Well,

Local or AD account you need an account that will successfully authenticate, which it seems to be able to, since you say you have a share..... The other part is having sufficient rights to read/write/do whatever you're trying to do...

I'd check the rights You could also make use of auditing (within windows) of the share(s) you're trying to access. The auditing logfiles would show you, when set up, what's happening between the client and the server.

/Rasmus

See my 5th post for my script I used after having the same trouble. It was the HP OEM partitions causing this for me.

http://altirigos.com/vbulletin...cating-connection.html

I tried a local account after seeing this worked for you and this has worked for me as well. I tried everything from all the KB articles, different domain accounts etc... It would work once and a while with a domain account, but usually fail at least 5 or 6 times before working. So far the local user(didn't even need admin) has worked each time.

I wonder if there is a problem with the way loginw.exe is passing the credentials in certain scenarios or environments with WinPE 2.1. When it would fail I could do a net use manually and that would work. Pretty odd.

Thanks.