I'm confused;  TSM doesn't support restoring system state to a different
hostname, so I don't know what would be considered "working as designed" in
that case!

How are you moving the registry?



On Thu, Jan 22, 2009 at 12:12 PM, Thomas Rupp <Thomas.Rupp AT illwerke DOT 
at>wrote:

> Hi TSM-ers,
>
> Environment:
> Client: Windows XP SP 2, TSM Client 5.5.1.0 and 5.5.1.6
> Server: Windows 2003, TSM Server 5.3.2.1.
>
> DSM.OPT:
> ENCRYPTIONTYPE: AES128
> ENCRYPTKEY: SAVE
>
> I understand that the encryption password is stored in the registry
> using the hostname to encrypt it.
> When I copy the TSM registry to another machine with another hostname I
> would like TSM to reject
> the encryption password because it was encrypted with the wrong
> hostname.
> But unfortunately TSM on the second machine is happy with the "wrong"
> encryption password and
> restores the data from the first machine without asking for an
> encryption password.
>
> Is this correct (works as designed) or should I report a bug?
>
> Thanks in advance
> Thomas Rupp
>
>
>
> Vorarlberger Illwerke Aktiengesellschaft ein Unternehmen von illwerke vkw
> Rechtsform: Aktiengesellschaft, Sitz: Bregenz, Firmenbuchnummer: FN 59202m
> Firmenbuchgericht: LG Feldkirch, DVR 0008753, UID-Nr.: ATU 36737402
>
> Vorarlberger Kraftwerke Aktiengesellschaft ein Unternehmen von illwerke vkw
> Rechtsform: Aktiengesellschaft, Sitz: Bregenz, Firmenbuchnummer: FN58920y
> Firmenbuchgericht: LG Feldkirch, DVR 0027961, UID-Nr.: ATU 36737304
>