Deployment Solution

Hey all

I've got a problem with the cmdlines.txt being overwritten when I run a scripted OS install job. The file usually contains the single command "AltirisAgent.bat SMP_Server.Domain.Local" which dumps the bootstrap files in the root of C:\. I've added a .REG file into the $OEM$ directory and put another line in the cmdlines.txt which will put it in the registry. 

The problem is when the scripted install starts the file on the package server that's running the job gets overwritten! I can see the modified date change and when I take a look at it there's only the original line in it. The weird thing is the version on the DS remains correct.

I'm using CMS 7.0 and DS 7.1 and I'm trying to do a scripted install of Windows Server 2003 R2 SP2.

Does anyonehave any ideas?

Thanks, 

Ollie

So you have a REG file, and a BAT file, and a cmdlines.txt file - 3 files, correct?  The bat file is altirisagent.bat, then there's a reg file somewhere - don't know what that is, and cmdlines.txt.  Right?

WHICH of thse is getting replaced?  Cmdlines.txt, or the bat file or the reg file?  And what do you mean by "the version on the DS remains the same"?  Did you mean the version on the NS - or the package source?  what is the directory structure you're using on the NS and/or package server for where these files are being stored?  And the file on the NS - is it identicle to the ones on the package servers, or are they unique?

Thanks!

Hey Thomas

I'll explain in a bit more detail. I've added OS files for Server 2003 R2. The DS has automatically created the i386\$OEM$ directory. Inside that are 'AltirisAgent.bat' and 'AltirisAgentInstBootstrap.cab' files and the cmdlines.txt. Initally the cmdlines.txt has the following in it:

I'm now wondering if we pull an updated file from the NSCap folder or something.  I'll have to peek around and see if we can tell what's happening there.

Sorry I don't have an answer yet.  Someone else might.  That's much more clear though.  Thanks!

That was my first thought, but I did a search for files called cmdlines.txt and the only ones that were found were in $OEM$ folders of OS files that I'd added. I couldn't find a master one.

Thanks.

If so, even if it "breaks" something, could you try without that piece and see if your cmdlines.txt file stays intact?  That might at least narrow down where the issue is.  Your thoughts?  Sorry if you already tried this - my brain is trying to balance too many issues simultaneously.  :P

Hey Thomas

DeployAnywhere isn't an option for scripted installes... :-)

One thought I did have was that there are A LOT of GUID folders in the SOI directory despite us only having 2 sets of OS files (Windows XP and Server 2003 R2). Since I'm new to this place I thought (perhaps) that someone might have added Server 2003 R2 OS files previously, kinda removed it and it's still there causing problems. I was going to delete all the GUIDs which don't relate to exising OS files.

Do you think this is worth a try?

Thanks

I realize its been more than a month since this was last updated, but I was wondering if you had figured out what was causing your cmdlines.txt file to be overwritten?

I'm runing into a somewhat similar situation whereby the AltirisAgent.bat script that is being pushed to the client is not valid and fails (see https://www-secure.symantec.com/connect/forums/windows-7-soi-not-installing-agent-automatically). This sounds a little like what you're saying was/is hapening, but it is a different file.

Thanks!

-Ned

Hey Ned

I'm afraid I didn't manage to get to the bottom of the problem. From the sound of the response from Thomas Baird it looks like it's a bug. Hopefully it'll be resolved eventually.

Sorry I can't help.

Ollie