Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Installing
Showing posts in English
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:

acsmcs | 21 Aug 2012 | 0 comments

In our Company we use Symantec Altiris Deployment Server 6.9

Once I came across the error 1223 Invalid Password. I followed the solution offered in the article TECH 26539 but it did not help as before the defaults were OK.

Our company has multiple physical sites that are on the same network but are on the different subnets and the computers on the site are not joined to the domain for the security reasons as the computers are used by the public.

After some research I found out that when the PC was trying to map a network drive it was using domain user account which did not exist on the Local Machine as the PC was not joined to the Domain.

The solution for this problem is to create same user account on the Local Machine with the same user name and password as on Domain.

vikasj | 05 Jan 2012 | 0 comments

We purchased an HP Compaq desktop which has Windows 7 and recovery partition buit in. We tried to deploy a Windows XP image on the same model but it fails every time after the completion of deploy image task.

In the Deployanywhere.txt logs we found critical drivers were missing, but all the necessary drivers were present in the Driverdsb.

Next we tried to install the operating system through our Volume License CD Key, but after verifying all Windows files it gives a blue dump. After that we found it is related to some Hard Disk setting in BIOS.

It is not a drivers problem.

We changed the BIOS SATA Emulation setting from AHCI to IDE mode and my image deployment problem on HP Compaq 6200 desktop with Windows 7 and recovery partition built in is quickly resolved.

On it I selected two tasks:
1. Deploy Image (Deployanywhere option should be ticked)
2. Reboot to production

Triinu Gross | 30 May 2011 | 0 comments

Barcode Solution lets you speed up asset data entry, reduce errors, track and audit assets, and manage your inventory. Barcode Solution is part of the following suites:

  • Altiris™ Asset Management Suite from Symantec™
  • Altiris™ IT Management Suite from Symantec™

Before you can use the features of Barcode Solution, you must set up your environment.

The article at the following link explains how to do that: Setting up Barcode Solution

EM-Pulse | 29 Mar 2011 | 0 comments

I noticed a discussion on here about having problems creating a WinPE boot disc for the Sony Vaio VPCZ1.

I solved this problem by downloading the HP drivers for the Intel 82577LC from here

On the GHOST boot wizard I added the Intel 82577LC driver gave it the friendly name of Intel 82577LC Vista 32 and pointed it to the Vista 32 driver that I extracted from the HP download  folder %\%\SP50479\flat\VISTAx32

To make sure nothing else would cause a...

mmathews | 13 May 2010 | 0 comments

Are you ready to upgrade to Altiris 7.0?
An important question to ask when considering upgrading, we don’t need to just rush into installation.  Too often, want to upgrade to the next best thing before all pieces have been put together, but should we even upgrade then?  Things to consider:

  • Is my environment ready?
  • SQL 2005 is required, do you have the licensing to upgrade or will that be an additional purchase?
  • Do I have current maintenance on my Altiris products where I will be able to upgrade?
  • Technical Knowledge?
  • Do I have the technical knowledge to troubleshoot if something breaks or will I constantly have to call support?
  • Maybe a professional technician who has experience with this install would be better
  • Do you have custom reports or code which could be broke which is business critical?
  • SQL Experience is a plus when migrating the database to...
CableGuy41 | 04 Jan 2010 | 2 comments

Hi All,

Check out the following link to know about how to Migrate an existing Wise Package Studio Server to a new server.

Please note: You will need to sign in to Linked in to view this article. If you aren't a member of Linked in you will need to signup (it's free).


Ludovic Ferre | 23 Dec 2009 | 1 comment

The path max_length limitation is well known, but interestingly enough Microsoft states that the 260 limit (including the "c:\" and line termination null char, so in effect it 256 chars from the current drive root) is not the maximum length possible for a path on Win32:

"Note  The maximum path of 32,767 characters is approximate, because the "\\?\" prefix may be expanded to a longer string by the system at run time, and this expansion 
applies to the total length.

The "\\?\" prefix can also be used with paths constructed according to the universal naming convention (UNC). To specify such a path using UNC, use the "\\?\UNC\" prefix. For example, "\\?\UNC\server\share", where "server" is the name of the computer and "share" is the name of the shared folder. These prefixes are not used as part of the path itself. They indicate that the path should be passed to the system with minimal...
Superfreak3 | 17 Dec 2009 | 0 comments
The biggest issue I've dealt with over the years is getting files to register properly via install.  I've used various authoring tools (mostly big name products) and I've had the same problem(s) with each - some more frequent than others.

For the most part, you add a file to your project/template and the information is scanned.  It never fails though, from release to release, I get one or two .dll's that just aren't getting registered.  I look in my project and it looks as though the registration stuff is there, but app errors so something not getting scanned/included properly.

I also noticed recently that when I pull an assembly into a template, it appears that registry information does get scanned for it.  However, I think its missing some 'stuff' that would be registered via RegAsm.  Being so busy since being called back from a layoff, I haven't been able to take registry snapshots to see what information is missing.


BRING | 16 Dec 2009 | 1 comment

After successfully installing ServiceDesk 7.0, and passing thru the evaluation time frame, or after applying a production-type license, the following error has been observed.

Error 1:

"License does not allow use of web part [SearchTextPortalWebPart] 

What are some suggested ideas to troubleshoot  this problem, since it makes using ServiceDesk impossible?

1. On the ServiceDesk Server, open up the Notification Server Credentials tool on the ServiceDesk server, and verify that the connectivity test for the Notification Server is successful.
       a.  If not, add the correct credentials and retry.  Suggested credential to use the the Altiris Application Identity (APPID) account.  This account should be a member of the local administrators group on the Symantec Management Platform Server (NS).
2. On the Servicedesk Server, open up the...