Video Screencast Help

Client Computer Name change not reflected in RS

Created: 07 May 2009 • Updated: 21 May 2010 | 7 comments

Running NS 6.0 SP3 + R8 and RS 6.2 SP2 with most hotfixes.

We're still in the process of rolling out RS.  Workstation name changes are not relected in any RS report, NS behaves fine.

Thanks in advance, Hai

Comments 7 CommentsJump to latest comment

KSchroeder's picture

Hait,
Does this persist after rebooting the client and taking a new snapshot?  You may have to run an AgentSetup.exe /reinstall to force the name to update.  Not sure, we don't do much with renaming machines.

Thanks,
Kyle
Symantec Trusted Advisor

For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.

alazanowski's picture

Altiris as far as i know only supports the "re-linking" of machines based on a particular name. From all the documents that i can find, you cannot take that SBSKey and have it re-linked to a machine name that is different, at least not with a stored procedure and they do not support back-end sql edits. Your best bet is to actually run a "new install" on the machine with the name changed, and it will create a new account with that workstation name.

-Austin Lazanowski Backups cost way too much until you needed them.

hait's picture

Thanks all, our situation is we use hotswap systems.  Building them in advance and renaming the system as needed. 

Kyle, even after reboot and new snapshots. 

I didn't think it was an issue because I thought RS was Guid based, but I see what you are saying Outbacker.

Thanks again, We will have to re-think our RS deployment and maintanence.

KSchroeder's picture

Well, not sure how Guid-based RS is.  It includes the NS Guid of the machine primarily (as far as I can tell) to help in linking the RS and NS computer identifiers in their respective databases (though for some reason the NSWrkstaGuid column in the SBS table is a string, not a GUID-type value in the database, so you have to CAST() it to UNIQUEIDENTIFIER).  RS seems to still exist and manage primarily on the SBSKey value.  Try making sure that the HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\eXpress\Recovery Solution Agent\SBSKey value is the same on the original and new machine, and that the GUIDs are the same.

Thanks,
Kyle
Symantec Trusted Advisor

For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.

Kenson's picture

I have the same problem please specify the solution.

KSchroeder's picture

So with these "hot swap" machines...do they have RS on them while in "standby" or do you re-install them to the original machine's account (agentsetup.exe /reinstall /server:rsserver /comp:"original-comp")?  Do you see the old machine's snapshot data?  I'm thinking that what might work better would be to reinstall the hot swap machine to the old machine's account, then do a Rollback to restore the user data.  We've used this method in the past instead of using Full System Recovery, and it has the advantage of generally being much faster than FSR.  There is a registry setting you have to set (ShowRedSnapshots); it is documented in the Altiris KB (https://kb.altiris.com).

Thanks,
Kyle
Symantec Trusted Advisor

For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.