Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

No c: and d: available after deployment server

Created: 20 Sep 2012 • Updated: 24 Sep 2012 | 8 comments
This issue has been solved. See solution.

We use Altiris version 6.9

After deployment of a server with  c: and d: disks, the disks are not present in Altiris properties.

However, the disks are present when you login to the server.

This problem causes the copy commands inside scripts to fail: path not found!

Any idea?

Comments 8 CommentsJump to latest comment

ianatkin's picture

Hi,

I've not seen this myself, but although I can see this being a problem for the "File Copy" tasks, I can't see how this is giving you issues within scripts (unless I guess you are using token replacements).

Can you,

  1. Post an example of the script you are using
  2. Tell us your target server operating system
  3. What agent you have installed on the server (AClient or DAgent)
  4. What the server hardware is

Kind Regards,
Ian./

Ian Atkin, IT Services, Oxford University, UK

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads

andykn101's picture

Add a "Get Inventory" Task in to your job after the image is deployed but before the scripts run. Then the Inventory record for the PC will get populated and DS will know it has C: and D: drives.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

SOLUTION
digimust's picture

Hi Andy, I think you solved the problem for me!

After adding "get Inventory" task the copy job worked fine!

I still don't understand why it worked fine and then all of a sudden no longer.

Many thanks to all posters.

ianatkin's picture

Hi Andy,

I've never had to do that before as the first thing the client does when it fires up is post an inventory. Is this a known issue?

 

Ian Atkin, IT Services, Oxford University, UK

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads

andykn101's picture

Not that I'm aware of but I remember having this exact problem a few years ago and I think that's what we did to fix it.

Alternatively, it may be that you need to split the Jobs so the Tasks that require the inventory to be posted are in a Job that doesn't start until the inventory is received. Maybe DS does an initial scan of Tasks in a Job when it's called and if the Inventory isn't posted unti halfway through the job DS has already decided to fail the Task. Or maybe it caches Inventory at the start of the Job.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

bhawver's picture

One other idea...if you are running a script, make sure that the script is not set to run "Locally on the Deployment Server".  I can see that potentially being an issue.  Other than that, as Ian had requested, it would help if that information was posted.  It would help eliminate the guess work.

 

Can you,

  1. Post an example of the script you are using
  2. Tell us your target server operating system
  3. What agent you have installed on the server (AClient or DAgent)
  4. What the server hardware is

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

digimust's picture

Ok bhawver and others the answers to you're questions:

1. See attachment for the copy script

2. target server OS: W2k3 and W2k8

3. Agent on server is DAgent

4. Target server hardware: HP Proliant DL380G6

Thanks for reactions so far!

cpy_script.PNG
bhawver's picture

Two things to try.  Number one...uncheck "Allow to run in automation".  You will want to ensure that it runs in the Production OS and not in Automation.  The other thing you might try is adding quotes around the entire path due to spaces being there.

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.