Deployment Solution

Hi to all Altiris users

I'm a old fox that work since years with Altiris Deployment.

At january 2009 we have updated our Altiris DS 6.9 sp1 with the Maintenance Pack 1 on a Windows 2003 Server.

At january2009, we have updated our Windows 2003 Cluster to Windows 2008 Cluster, but Altiris Deployment 6.9 sp1 is still on a Windows 2003 server.

The problem is that we can't connect a additional network drive when we work with DOS to deploy our images. The command is "NET USE x: \\server_name\share" and thhe displayed message is:

"Error 3: The specified path was not found.
An error occured accessing the security-settings files."



Because we have images on our Windows 2008 server, we have forced to connect this additional drive in the mapdrv.bat file.

Have anybody the same problem or maybe the solution?

Kind regards,
Hubert CLEMENT / Technical engineer / University of Fribourg /Switzerland

The error you are mentioning leads me to believe that the credentials are not working. Has the password changed recently? Or possibly domain the domain?

Hello,

Thank you for your question. Our domain and accout are the same, we don't change it.

The problem is, that Windows 2008 clustering have a high security level and that we can't to join directly the shared ressource.

I hope that my response help you? Kind regards,

Hubert

You might change the command to: net use x: \\servername\share /user:username password

Be sure to assign a specific account that doesn't have rights to anything else to this. Also, if you don't want the username and password visible when the script runs put this instead: @net use x: \\servername\share /user:username password

If that doesn't work, you may need to put the domain name in with the username like so: @net use x: \\servername\share /user:DOMAIN\username password

Hi, Hubert..

I also ran into this issue, and so decided to think a little outside the box.

I had need of mapping an extra drive letter based on IP, which I ran as a KIX16 script..
The issue arose where the script would establish which server to use, but couldn't actually connect to it because of the user details..

Long story short, here's what I did:

In the boot disk creator, edit the STARTNET.BAT file..

Scroll down to:
REM Map network drives
echo Mapping network drives...
if exist %net%:\mapdrv.bat call %net%:\mapdrv.bat

and then I added:
if exist f:\drivers\hii\dos\mappxe.bat call f:\drivers\hii\dos\mappxe.bat

where f:\drivers\hii\dos\mappxe.bat is the secondary mapping script hosted on the express share.

The real advantage of this method is that if I needed to alter the mapping script, I didn't need to re-edit the boot disks.

It's far from elegant, but it works for me, so who cares?

Any use?

Regards,
Gerard