How to install a client on 64 bit system
Updated: 21 May 2010 | 6 comments
This issue has been solved. See solution.
Hello,
I have a short question. Since a few days we have 64Bit systems in our environment. We install the client like before on the 32 bit system under the path:
C:\program files\altiris
Is this still ok?
Or is it necessary to install it under
C:\program files (x86)\altiris
Because we saw later that if Altiris is deploying additional solutions after the initial installation all this solutions will installed under c:\program files (x86).
(See screenshot)
What is the recommendation? Best practices? Is it wrong to install the client under program files?
Thx and regards,
Toka
discussion Filed Under:
Comments
Non-native (read 32bit) programs should always be installed under (x86). If you manually install it to a different directory, does the system still report? I've never bothered to do it that way.
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.
Ok this was my question.
In the meanwhile I found the reason why the package was installed under the wrong folder.
I started the installation with the following string
%\..\AeXnsc.exe -s -a ns="SERVERNAME" nsweb="SERVERNAME:2099/Altiris" path=c:\program files\altiris\altiris agent
So I change it into
%\..\AeXnsc.exe -s -a ns="SERVERNAME" nsweb="SERVERNAME:2099/Altiris"
Now Altiris will be installed under \\program files (x86)
BUT
I still have the folder \program files\altiris
In this forlder you find \altiris agent\tasks
Why the hell ist that folder still on this location??? Is that a must? Or still a misconfiguration??
Hi ToKa,
I have the same problem. It makes no different if I use the path or not. I found the value in the registry where the path to the tasks are set. I couldn't handle to install it the right way. I have only one idea that maybe it's realted to the client version. Let us see what we get.
Can each of you please let me know what OS you are trying this on? Also did you do a complete removal of the agent before the second install?
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.
Hi Jharings,
I use windows 2003 R2 SP2 and I start first with no client. For the removal I use the command AexagentUtil.exe /clean. After that I remove the folders and try the second installation. If you have other advice please let me know.
Regards Marc
Symantec responded to my request for information about this issue. Based on the information in the thread, they were unable to reproduce the problem. They have requested that one or both of you open up a support incident, and if it does end up being a bug, then you won't be charged.
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.
Would you like to reply?
Login or Register to post your comment.