Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Altiris DS 6.9 SP1 - Migrating the eXpress Share from one Disk to another

Updated: 27 Sep 2010 | 11 comments
Arfag's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Due to lack of space on the current partition where the eXpress share is located we need to migrate it to a another partition with more space.
The plan is :
-Backup eXpress DB and file structure of the server.
-Copy all contents of the DS Share (PXE Image files, SW Packages, eXpress Share file..and so on) to the new partition. The Software Packages are located on the eXpress share and are replicated via NS to all Package Servers. 
-Once all files have been copied to the new location the DS services will be stopped.
-The new partition will be renamed to the previous name of the drive where the current share is located. All required shares will be created.
-The 'old' partition where the eXpress share was copied from will be renamed.
-Altiris DS services will be restarted.

Have you done \ seen this before? If yes, could you please advice if the foreseen plan is adequate in order to smoothly migrate the share? Whate else should be considered?

Thank you for your valuable help.

Comments

aspen's picture
26
Oct
2009
0 Votes 0
Login to vote

I have done this before

I have done the same process but not in entirely similar circumstances. The importand thing is that the new partition has the same drive letter as the old one. After that if all data is mirrored you should be ok.

Of course you should make sure that before you do this process that you turn the DS services OFF and that all data has been backe dup and able to be restored if needed.

Arfag's picture
28
Oct
2009
0 Votes 0
Login to vote

Aspen, Many thanks for your

Aspen,

Many thanks for your reply. We will accomplish this task on the weekend adn I will update this post.

Thanks

Arfag's picture
16
Nov
2009
0 Votes 0
Login to vote

Hi All, So it's done. This

Hi All,

So it's done. This morning I came in and restarted all DS Services on the server in question. Then, I performed multiple tests on the finctionality of DS with success.
However, an issue has come up when starting the PXE Configuration Utility I receive the following error message:
"The PXE Manager has not connected with the DS Server..." I checked AKB #2165 and followed the instructions there..There was nothing changed on the server..The pxemanager.ini is the same as the one prior to the mogration. Clients are still booted to PXE and can be rolled out. Both services Ds DB Manager and PXE Manager are up and running..However, there is no way to open the PXE Configuration Utility..!!

Does anybody have an idea as how to correct this issue?y At the moment we do not intend to reinstall the PXe Manager as it worked fine sofar, and, we do not want to recreate the pxe boot files again.

Thank you for your help.

 

ianatkin's picture
16
Nov
2009
0 Votes 0
Login to vote

 Hi, Yeah -the PXE Manager

 Hi,

Yeah -the PXE Manager can be a bit fickle. Could you post the PXE Manager logs? The location can vary depending on your configuration, but they are typically in the PXE folder on the express share, PXELog_Manager.txt

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&

Arfag's picture
17
Nov
2009
0 Votes 0
Login to vote

Hi Ian, Thank you for your

Hi Ian,

Thank you for your feedback. The last enteries of the aforementioned log file are included in this post. There is no further Information in this log.

==
E [13:55:38 11/16] (4652):   Session ID: 1258376138
E [13:55:38 11/16] (4652):   DSServerIP: x.x.x.x
E [13:55:38 11/16] (4652): PXEManagerIP: x.x.x.x
E [13:59:56 11/16] (4536):   Session ID: 1258376396
E [13:59:56 11/16] (4536):   DSServerIP: x.x.x.x
E [13:59:56 11/16] (4536): PXEManagerIP: x.x.x.x
===
As I can see these entries are not really informative. The IP addresses are correct...

Thanks.

ianatkin's picture
17
Nov
2009
0 Votes 0
Login to vote

 OK -we need to increase you

 OK -we need to increase you logging level from Errors only to Information. On your server do the following,

  1. Stop the Altiris PXE Manager Service
  2. Locate the PxeManager.ini
  3. Find the loging entry for the PXE Manager Log and ensure the OutPutThreshold is set to 3 (will probably be 1 currently) as below,
    PxeManagerLog_Enabled=True
    PxeManagerLog_OutputThreshold=3
    PxeManagerLog_FileName="PxeLog_Manager.Txt"
  4. Start the PXE Manger Service

If you now post your new log, then this might contain something which can help troubleshoot further.

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&

Arfag's picture
17
Nov
2009
0 Votes 0
Login to vote

Hi Ian, Thank you for your

Hi Ian,

Thank you for your help. I have increased the logging level for PXE and received the included message on the file.
There is an authetication failure, which indicates a serverkey or\and MMACESSKEY issue. 
Here are the results in the log file when I start the PXE Config Utility:
---------------------------
Request=Authenticate
Type=PxeManager
CipherText=xxxxxxxxxxxxxxxxxxx
=========== End Request =========
I [13:22:53 11/17] (7828): Message Received: (91:1)
========== Begin Message ========
Processing=Authenticate
=========== End Message =========
I [13:22:53 11/17] (7828): Message Received: (92:1)
========== Begin Message ========
Reply=Authenticate
CipherText=
Result=Failure
End Message
=================================================
 
 

ianatkin's picture
17
Nov
2009
1 Vote -1
Login to vote

PXEKeyMatch utility

It looks like you've got a problem with your security keys on the server.  The first step to resolving this it to try resyncing the DS security key which is used in communications with the PXE Manager service.

You might find the Utility PXEKEYMATCH.EXE in the tech support folder on your deployment server, if not it can be downloaded from KB19228 

I'm a bit hazy on its use, but to be safe I'd

  1. stop all the Altiris Services
  2. Open up a command prompt, and CD into the folder with the pxekeymatch.exe utility
  3. type pxekeymatch -sync
  4. Reboot the server

These instructions are perhaps a but over-zealous, but if you follow them we'll at least know whether a sync suffices, or whether we need to regenerate your security keys from scratch.

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&

Arfag's picture
17
Nov
2009
0 Votes 0
Login to vote

Hi Ian, I appreciate your

Hi Ian,

I appreciate your help. As Ds serves more than 4000 clients we have already announced that we will perform maintenance work on DS by the end of this week. I will keep you updated.

Kind Regards, 

Syc's picture
25
Mar
2010
0 Votes 0
Login to vote

I have same problem. I added

I have same problem. I added new array to server (TMP to copy data there). After restart PXE was down but it was possible to start that.
I removed original array and now I have same problem.

Sync keys does not help...

regards,
Syc

Syc's picture
26
Mar
2010
0 Votes 0
Login to vote

FIXED for now

mapped original disk as W:

 

stop all Altiris* services

restore folder D:\Altiris\eXpress\Deployment Server\PXE from W:\Altiris\eXpress\Deployment Server\PXE

PxeKeyMatch.exe to sync

start all Altiris services but not PXE

PXEManager.ini ->  copy key there from MMAccessKey.ini

start PXE Mananger

start PXE Helper