Software delivery... need 64bit CMD
Updated: 30 Sep 2010 | 7 comments
I am trying to build a software deliver job for our windows 7 64bit client machines that will install and configure the Remote Admin Tools using DISM. The problem is that Altiris causes the batch to run in 32-bit instead of the 64-bit. Is there a way around this?
Batch file:
------------------------
@ECHO OFF
ECHO Install 64bit Admin Tool Pack
amd64fre_GRMRSATX_MSU.msu /quiet
amd64fre_GRMRSATX_MSU.msu /quiet
ECHO Enabling Features
dism /online /enable-feature /featurename:RemoteServerAdministrationTools /featurename:RemoteServerAdministrationTools-Roles /featurename:RemoteServerAdministrationTools-Roles-AD /featurename:RemoteServerAdministrationTools /featurename:RemoteServerAdministrationTools-Roles /featurename:RemoteServerAdministrationTools-Roles-AD-DS /featurename:RemoteServerAdministrationTools /featurename:RemoteServerAdministrationTools-Roles /featurename:RemoteServerAdministrationTools-Roles-AD-DS-SnapIns
dism /online /enable-feature /featurename:RemoteServerAdministrationTools /featurename:RemoteServerAdministrationTools-Features /featurename:RemoteServerAdministrationTools-Features-BitLocker
discussion Filed Under:
Comments
Probably not until a true 64bit agent is released
which I believe is on the roadmap for a release this year. I doubt that you can force the program to run in a 64bit space, if the Altiris agent itself cannot.
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
Your batch file is ???
Hi Mate
Have you called your batch file .cmd or .bat ?
This might sound irrelavant, but it actually isn't, the problem is if you call your batch file .bat it is executed via command.com instead of cmd.exe.
/Morten
The other workaround for this
The other workaround for this is to call cmd.exe from the command line like so:
\\%COMPUTERNAME%\ADMIN$\system32\cmd.exe /c "yourexe.exe"
Since the AAgent is currently a 32bit application, it can only see (by default) 32bit sections of the system.
Thanks,
Kyle
Symantec Trusted Advisor
For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.
Also see AKB39284 for some
Also see AKB39284 for some additional details. Not sure that the \\%COMPUTERNAME% will work; the referenced KB suggests using \\127.0.0.1\admin$\system32\ instead so maybe try that as an alternative.
Thanks,
Kyle
Symantec Trusted Advisor
For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.
This is the solution
We had to use this KB for inventorying 64-bit machines before Inventory Solution supported it after a recent service pack. We could never hammer down why there were a few machines who simply refused to run the task by IP address, though. We wound up using localhost with no problems.
--Dave
I will try the loop back IP
I will try the loop back IP option later this week. In the mean time I just used DS to run the install since the DAgent is 64bit. :-)
Thanks
Let us know how it worked out for you.
Thanks,
Kyle
Symantec Trusted Advisor
For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.
Would you like to reply?
Login or Register to post your comment.