Video Screencast Help
Endpoint Management Community Blog
Showing posts in English
ianatkin | 25 Jul 2014 | 1 comment

Last week saw us having a few festivities to mark the end of a major project here; our XP to Windows 7 migration. We're all pretty chuffed with what we've achieved here; a very smooth user upgrade with remarkably few hitches considering from start to finish the project of migrating nearly 2900 machines took 7 months. 

Windows7_Rollout_1.png

This really was a remarkable success. The target time to migrate a user's desktop from XP to Windows 7 was set at 1hr, and this average time was to hold no matter what the site link speed was, and despite the fact that machines would be competing with up to 15 machines being deployed concurrenty.

Most of the migrations were also complicated by the fact that they were at user's desks which were distributed across 50 sites. To enable the deskside techs to focus on confirming machine configuration, specialist software requirements, and...

ianatkin | 25 Jul 2014 | 2 comments

 

When we upgraded our production SMP server from 7.5HF2 to 7.5SP1 we noticed a lot of errors sloshing around our event logs in the days that followed,

  1. Access Denied: No Permission to view task history
  2. Unhandled Exception: An entry with the same key already exists
  3. Unable to create menu item as there due to an XML schema error. An entry with the same key already exists

 

LOGVIEWER.png

The first error initially dominated the logs (occuring every few seconds) and then it eased, becoming less frequent (perhaps hourly) and sporadic.

The second and third errors always occured together and only started appearing once the techs started using the console following the upgrade. It turned out that these two errors conincided with a broken resource manager. When console users double-clicked a computer...

Kevin Haysmer | 24 Jul 2014 | 0 comments

I started to hunt as many have before for a custom inventory for Altiris 7.1 that would get the Autodesk information like in Altiris 6.5. Every time I thought I had the script working I would find a different product it was not getting the information on correctly. Or in some case it just would not read a registry field like it would all the others. As I started to look I found the reason was not all the registry fields patterns where the same in about 2012 they changed the format of the registry configuration. There are also other products in Autodesk that the path in the registry was different or the field I wanted had a different name from one product to the next. So I started to compile a list of all the software I may need and looked for the registry keys I would need to make a functional custom inventory script for Autodesk. Just so we can all get it out yes I know I could have broken parts of this down into functions and had the script shorter but at the time I was not...

kedar_k | 21 Jul 2014 | 8 comments

ITMS 7.5 SP1 HF1 is available through SIM. It has the fix for the following issue:

DOC7555.JPG

You can access the ITMS 7.5 SP1 HF1 release notes from the following location:

Symantec™ IT Management Suite 7.5 SP1 HF1 powered by Altiris™ technology Release Notes

-

You can access the ITMS 7.5 SP1 HF2 release notes from the following location:

Symantec™ IT Management Suite 7.5 SP1 HF2 powered by Altiris™ technology Release Notes

ryanschoenherr | 09 Jul 2014 | 0 comments

Join our webinar on July 29th @ 11AM EST to learn about our Universal Imaging Solution.

 

                                            REGISTER HERE NOW!

         

            Screen Shot 2014-07-09 at 2.53.51 PM.png

Screen Shot 2014-07-09 at 2.48.48 PM.png

ianatkin | 07 Jul 2014 | 2 comments

 

One of the things about writing DS jobs in a rush is that the end result is often really difficult to repurpose and port to other servers. This is because my DS jobs contain many tasks; so rushing inevitably means that many aspects are hard-coded. 

As a programmer having hardcoded elements distributed throughout a complex job goes against the grain; when programming I try to place all those nice user-editble variables at the start to make it clear that only one area needs attention when changing simple items like file locations.

However this is tricky to do with DS... sharing user variables between the client production, automation and the server is just plain awkward. In the past I've tried various routes to get around this,

  1. Creating on the fly and environment variable batch script (named %ID%_env.bat) on the deployment share. This hosts all the user-editable variables and can be called at the start of each script task to ensure...
ianatkin | 07 Jul 2014 | 0 comments

I came across this news last month and was a bit dissapointed. I was aiming to move to Zone just before this accouncement came as I very much liked the idea of holding my own encryption keys. Unlike with some other cloud storage providers, my stuff would remain always remain my stuff in the zone.

If you are a Norton Zone customer, today (7th July) sadly marks the beginning of the end. According to the Zone placeholder page, from today you'll no longer be able to share files or create public links. The end itself comes in one month on the 6th of August at which point Symantec will terminate the service and delete any remaining Zone files.

My heart goes out to all those who shed sweat developing this product.

Full details on http://www.nortonzone.com/

Kind Regards,
Ian./

ianatkin | 02 Jul 2014 | 15 comments

Just imported some job binary for normally well behaved jobs on a new DS6.9 SP6 server (on Windows 2008 R2 with SQL Server 2012) and started getting this error on tasks running embedded scripts.

Never seen this before which is odd as I've been using these job sets for years (since SP4). It's an access denied problem...  and sometimes it happens... sometimes it doesn't.

Feels like a support ticket is looming... :-(

kedar_k | 19 Jun 2014 | 0 comments

Migration: A migration is when you install the latest version of the IT Management Suite solutions on a new server, and then migrate the data from the earlier ITMS solutions to the latest version of the application.

Upgrade: An upgrade is when you install the latest version of ITMS on the same hardware, server operating system, and database.

You must migrate the Notification Server 6.x or 7.0 data to either Notification Server 7.1 SP2 or Notification Server 7.5. After migrating the data, you must first upgrade to either ITMS 7.1 SP2 MP1.1 or ITMS 7.5 HF6 depending on the path you choose and then upgrade to ITMS 7.5 SP1.

The following diagram gives an overview of the migration and upgrade process:

Migrating to IT Management Suite 7.5 SP1

You can use the following reference documents:

...
ryanschoenherr | 18 Jun 2014 | 0 comments

Join Novacoast on June 24th, at 11am EST for an Altiris 7.5 webinar

- Follow the link below to register

         http://connect.novacoast.com/altiris-upgrade-webinar

                       

 

                 New features & Why theres no better time to upgrade!

Cloud Enabled Management - Manage clients outside the corporate network

Macintosh Support - Deploy, Manage and Secure your Macs

Updated Deployment Solution - Easier to use, support for Mac

Better Performance - Faster, more scalability, manage more endpoints

New Platform Support - For the newest Windows, Mac and Red Hat operating systems

Workflow...