Deployment Solution 6.9 SP1 is Available
Updated: 29 Oct 2008 | 12 comments
It looks like DS 6.9 SP1 has been released and is available on Altiris' download page. http://www.altiris.com/Download.aspx
Release notes Article ID: 42696 https://kb.altiris.com/display/1/index.asp?c=&cpc=...
blog entry Filed Under:
About Endpoint Management Community Blog
The Endpoint Management Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Endpoint Management community. Any authenticated Connect member can contribute to this blog. Filter by:
Blog Tags
Configuring Altiris Client Management Suite Altiris Deployment Solution Symantec Management Platform (Notification Server) Wise Packaging Basics Altiris Server Management Suite Best Practice Compatibility Tip/How to Helpdesk Solution Altiris IT Asset Management Installing Workflow Solution Ghost Solution Suite Windows Reporting Performance Upgrade Features ServiceDesk 7.x Database Agents Dell Management Products
Comments
Upgrade went well!
After reading over the upgrade part in the KB everything well smooth:
Upgrade Installations:
When you are performing an upgrade or installing another Deployment Solution version, ensure that you don't have a remote console running. The remote console must be shut down before you try to upgrade or reinstall the Deployment Solution software.
Stop the following services on your Deployment Server before starting the upgrade process: Altiris Deployment Server Data Manager, Altiris Deployment Server DBManagement, Altiris Express Server, Altiris PXE Server, Altiris PXE Manager, Altiris Config Helper, and Altiris PXE MTFTP Server.
Everything went well it took me about a hour and half from start to finish, which also includes upgrading the Altiris dagents (version 6.9.355).
Thanks, Chris Bashlor
Few minor problems
There are a few minor problems I have had with the 6.9 SP1. (I upgraded from 6.9 if that matters)
1. Currently WinPE is now working for me and I have a call in with Symantec to get this fixed. The guy that is working on my case did some testing and had the same problems, just a heads up.
2.Another problems is the compatibility with the current ASDK. Another issue that forced me to opened an incident with Symantec.
3. The last problem I have ran into is with HIIS. Because of the security changes, HIIS can no longer pull drivers from computers on the network. I am trying to work with them to get this resolved. Through my testing I did verify that this is not a problem if DS security is disabled. Also a small work around is to change the credentials the job uses and restart the job, so it is not too big of a deal.
~4. A problem I am at this very moment running into is my 64 bit computers are not telling the DS that there is a job running on them for PXE. One kept forcing me to hit F8, when it should have just booted to my Linux PXE the other kept trying to running initial deploy. I don't recall having this problem with the 32 bit computers, but I will having to do more testing on this problem before I call it in. This might just be something I did, (like a faulty configuration on my part) so it might not really be a problem.
Problems with WinPE
I am also having problems with WinPE 2.1. With the help of tech support they got WinPE 1.6 working, but not 2.1
John Atkins
Advanced Client Services Engineer
LifeWay Christian Resources
http://www.lifeway.com
TN User Group Membership Director
I'm pretty surprised they
I'm pretty surprised they released a final candidate with so many problems. I wanted to install it but looks like I'll be waiting for bugs to be quashed.
Thanks for the heads up though.
I'm not surprised... ;-)
Altiris are good at many things, but vigourous testing has historically not been one of them.
From here on though, upgrades should be smoother. Symantec have demanded an in-house rollout for the NS7/DS7 products before public release.
This delays the release to market, but I hope this is a policy they will continue into the future. Being a DS/NS administrator has historically required you to become Troubleshooter Extrordinaire! I'd frankly like to do less troubleshooting, and more implementing.
Kind Regards,
Ian./
Ian Atkin, Senior Developer for the ICT Support Team, 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&
Yep - Testing process is not TOP, I confirm localization bugs...
FYI, if you install in French or German OS Windows, you will have some problems, like: HP clients with Yellow icons instead of blue temporary license icon; no complete inventory, without all serials; Aclient does not auto update on clients... Just change regional language to US on your DS host (all the same FR or GE OS); rerun DS 6.9.355 sp1 install: magically working all well. You can back regional to FR or GE to reload your language. But do the install in English ;-)
~Pascal @ Bechtle~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF&l
Problems in NS after installing
Deployment solution now no longer shows as installed in NS, doesn anyone know how to rectify this one relatively quickly? Without NS knowing about it there are no migration tasks for the DS agents etc in NS anymore.
Not an NS Specialist
I am not an NS Specialist by far but from what I have understood about the NS is that there is not integration with the DS yet, that is coming in 7. As far as deploying the DS agents in the NS all the NS looks for is if the files exist or if it is installed, not that the DS is any part of the NS (not really). I could be wrong, wouldn't be the first time but I am pretty sure the DS and the NS do not communicate. At least I hope not, because we have both and I have not done anything to make sure that they do talk to each other..
There's a good deal of
There's a good deal of integration already actually, there's already a "deployment solution" view in 6.5, and an integrated deployment console. There are plenty of reports and tasks available to make life easier - the very handiest of which for me are the migration tasks for DS agents. We plan to move DS to another server soon and this will be essential. The most odd thing is DS is not even showing up as installed on the solution centre view for us currently. It's probably a simple fix and not even related to 6.9 SP1, but with my limited knowledge of setting the two up together I'm going to be stuck!
Error 32 when upgrading AClient
After upgrading DS to 6.9 SP1, it attempted to auto update the clients. And now the majority of my users are getting errors: "Error 32 copying new AClient.exe!"
Anybody run into this before? Any ideas?
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.
And in other bad news....
And in other bad news.... DS has been completely unstable since, constant axengine.exe crashes, as far as I can tell it's only when imaging jobs are being sent and possibly related to the deployment console in NS specifically. I don't suppose any of the previous hotfixes will work as these should be a part of 6.9.355 as standard right?
Will post here if I find the fix, currently looking at just migrating but am sending everyone to the DSweb console direct now to see if the integration breakdown is the cause of the crashes.
hotfix!
for anyone else that encounters this problem when the DS web console and 6.9 SP1 is installed and running, see KB Article 44109.
So far so good for us, though I'll post in a few days if I think any different after it starts being used heavily.
Good luck!
Would you like to reply?
Login or Register to post your comment.