Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Windows\s+2003\s+Encryption\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Windows\s+2003\s+Encryption\s*$/: 20 ]

Total 20 documents matching your query.

1. Windows 2003 Encryption (score: 1): Author: Roger Silva <rogsilva AT STANFORD DOT EDU>; Date: Thu, 5 Oct 2006 13:33:08 -0700; My client is running Windows 2003 client OS Version 5.02 and our TSM server is 5.1.6.3 We are trying to use the TSM Encryption Options but we are running into some issues. We have the Encryption line; /lists/html/ADSM-L/2006-10/msg00080.html (9,905 bytes)
2. Re: Windows 2003 Encryption (score: 1): Author: Andrew Raibeck <storman AT US.IBM DOT COM>; Date: Thu, 5 Oct 2006 14:44:31 -0600; Do you actually have a directory called "test spreadsheet.xls" ? Probably not contributing to the issue, but your exclude.backup statement should be corrected to read: exclude.backup *:\...\* Regards; /lists/html/ADSM-L/2006-10/msg00081.html (11,246 bytes)
3. Re: Windows 2003 Encryption (score: 1): Author: Roger Silva <rogsilva AT STANFORD DOT EDU>; Date: Thu, 5 Oct 2006 14:11:36 -0700; Andy, The main directory in D:\1TSMTEST, spreadsheet.xls is just a file within that directory that we are trying to do a test encryption on. Let me also state that the TSM Software is installed on th; /lists/html/ADSM-L/2006-10/msg00082.html (12,125 bytes)
4. Re: Windows 2003 Encryption (score: 1): Author: Andrew Raibeck <storman AT US.IBM DOT COM>; Date: Thu, 5 Oct 2006 15:18:18 -0600; It isn't the encryption of one file that is the issue, it's the syntax of the include.encrypt line. They way it currently reads: Include.Encryption "D:\1TSMTEST\test spreadsheet.xls\...\*" says to en; /lists/html/ADSM-L/2006-10/msg00083.html (14,046 bytes)
5. Re: Windows 2003 Encryption (score: 1): Author: Roger Silva <rogsilva AT STANFORD DOT EDU>; Date: Thu, 5 Oct 2006 14:48:08 -0700; Thanks Andrew, I will make the changes and let you know the outcome. Thanks, Roger It isn't the encryption of one file that is the issue, it's the syntax of the include.encrypt line. They way it curr; /lists/html/ADSM-L/2006-10/msg00084.html (15,498 bytes)
6. Re: Windows 2003 Encryption (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Thu, 5 Oct 2006 19:30:53 -0400; Roger - I don't believe that you have been as successful as you think you have been... The ENCRYPTIONType option was introduced in TSM 5.3. You must be getting 56-bit DES encryption, then. I'm surpri; /lists/html/ADSM-L/2006-10/msg00085.html (11,526 bytes)
7. Re: Windows 2003 Encryption (score: 1): Author: Roger Silva <rogsilva AT STANFORD DOT EDU>; Date: Thu, 5 Oct 2006 17:14:01 -0700; Richard, My client TSM Version is 5.3.4 which says it supports AES128 Bit Encryption, am I wrong? Also, here is a snippet of the "show options" command. ENABLECLIENTENCRYPTKEY: NO ENCRYPTIONTYPE: AES; /lists/html/ADSM-L/2006-10/msg00086.html (12,170 bytes)
8. Re: Windows 2003 Encryption (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Fri, 6 Oct 2006 09:28:50 -0400; Richard, My client TSM Version is 5.3.4 which says it supports AES128 Bit Encryption, am I wrong? Roger - This is your first posting citing the TSM level of that TSM client. I had gotten the impress; /lists/html/ADSM-L/2006-10/msg00091.html (11,008 bytes)
9. Re: Windows 2003 Encryption (score: 1): Author: Roger Silva <rogsilva AT STANFORD DOT EDU>; Date: Fri, 6 Oct 2006 07:06:06 -0700; Richard, Sorry for the confusion. Yes, it does scare me that if the Encrypted Password is forgotten, that the data is unrecoverable, but this is data that has to be safely backed up and stored via HI; /lists/html/ADSM-L/2006-10/msg00092.html (11,821 bytes)
10. Re: Windows 2003 Encryption (score: 1): Author: Roger Silva <rogsilva AT STANFORD DOT EDU>; Date: Fri, 6 Oct 2006 10:08:41 -0700; Andrew, I changed the parameters per you email and it worked. Thank you very much. I do, however, have one more question. My client has asked me if there is a way to export the EncryptKey but I have; /lists/html/ADSM-L/2006-10/msg00098.html (16,197 bytes)
11. Windows 2003 Encryption (score: 1): Author: Roger Silva <rogsilva AT STANFORD DOT EDU>; Date: Fri, 6 Oct 2006 11:28:18 -0700; Hi, My client has asked me if there is a way to export the EncryptKey but I have not found any documention talking about this. The reason for this I assume would be in case of a system crash. I know; /lists/html/ADSM-L/2006-10/msg00103.html (10,608 bytes)
12. Re: Windows 2003 Encryption (score: 1): Author: TSM_User <tsm_user AT YAHOO DOT COM>; Date: Sat, 7 Oct 2006 09:18:22 -0700; Roger, I believe the encryption key for the regular BA Client is not kept seperate on the TSM server. Only the Tivoli Data Protection (TDP) software, which supports transparent encryption, store the; /lists/html/ADSM-L/2006-10/msg00110.html (17,340 bytes)
13. Re: Windows 2003 Encryption (score: 1): Author: TSM_User <tsm_user AT YAHOO DOT COM>; Date: Sun, 8 Oct 2006 19:11:25 -0700; To your question you only need the value you typed to generate the key the first time. You will be prompted to type it again and it will then encrypt the key again and store it in the registry. Entri; /lists/html/ADSM-L/2006-10/msg00114.html (11,191 bytes)
14. Re: Windows 2003 Encryption (score: 1): Author: Roger Silva <rogsilva AT STANFORD DOT EDU>; Date: Sun, 8 Oct 2006 20:44:35 -0700; Thank you for the info. I'll look into the MS regedit for exporting/importing and see if the client wants to do this or if they will just keep the password phrase used somewhere and just use that if; /lists/html/ADSM-L/2006-10/msg00115.html (11,613 bytes)
15. Re: Windows 2003 Encryption (score: 1): Author: Andrew Raibeck <storman AT US.IBM DOT COM>; Date: Tue, 10 Oct 2006 08:38:14 -0600; No, you cannot just export/import the registry key. See the README file for the 5.3.4.x clients and look for the bullet titled "ENCRYPTKEY SAVE requirements". Also look up APAR IC48782. Regards, Andy; /lists/html/ADSM-L/2006-10/msg00134.html (12,696 bytes)
16. Re: Windows 2003 Encryption (score: 1): Author: Roger Silva <rogsilva AT STANFORD DOT EDU>; Date: Tue, 10 Oct 2006 08:17:18 -0700; Thanks Andy, From what I understand, you cannot encrypt the systemobjects which would include the registry, is this the case and if so, is there a way around this in order to secure that your registr; /lists/html/ADSM-L/2006-10/msg00135.html (13,601 bytes)
17. Re: Windows 2003 Encryption (score: 1): Author: TSM_User <tsm_user AT YAHOO DOT COM>; Date: Wed, 11 Oct 2006 19:47:27 -0700; I read that APAR but it makes it sound like if the computer name is the same then the key will work. So if you exported the key and then imported it on a server that you were recovering so the name w; /lists/html/ADSM-L/2006-10/msg00179.html (12,761 bytes)
18. Re: Windows 2003 Encryption (score: 1): Author: Andrew Raibeck <storman AT US.IBM DOT COM>; Date: Thu, 12 Oct 2006 14:32:59 -0600; Since Windows 2003 system state backup is an "all or nothing" affair, unchecking "Back up the Registry" has no effect (that should actually come out, since it applies only to NT 4.0, which is not sup; /lists/html/ADSM-L/2006-10/msg00209.html (15,171 bytes)
19. Re: Windows 2003 Encryption (score: 1): Author: Andrew Raibeck <storman AT US.IBM DOT COM>; Date: Thu, 12 Oct 2006 14:39:22 -0600; In theory, yes, it should work. But this is not a scenario that we intended to support, so it hasn't been tested. You can try it and see how well it works, but at this time, I can not officially reco; /lists/html/ADSM-L/2006-10/msg00210.html (14,152 bytes)
20. Re: Windows 2003 Encryption (score: 1): Author: Roger Silva <rogsilva AT STANFORD DOT EDU>; Date: Thu, 12 Oct 2006 15:28:10 -0700; Ah, Good to know. Thanks Andy for you help. -Roger Since Windows 2003 system state backup is an "all or nothing" affair, unchecking "Back up the Registry" has no effect (that should actually come out; /lists/html/ADSM-L/2006-10/msg00214.html (18,928 bytes)

Current List: 1 - 20
Page: [1]