Re: Windows XP - User Backup & Restore

2002-07-29 Thread Dirk Kastens

Hi,

> In the laboratory, I have been able to install the
> central scheduling service and can backup/restore all
> files as an administrator. When I'm logged in as a
> power user, it's a different story - I am only able to
> backup/restore such System Objects as thr Registry,
> COM+ DB, Event Log, Registry, System Files and WMI.

Same on our W2k workstations. Users can only backup
their files after creating shares for the local
drives, like "drive_c$". Then these shares appear in
the client GUI and can be backed up. The solution
with the registry keys didn't work for us.

Regards,
Dirk Kastens



Windows XP - User Backup & Restore

2002-07-29 Thread Douglas Currell

Still having problems with TSM and Windows XP
clients..

To rehash:

My organization is planning a rollout of Windows XP
for the desktop. The users are currently using Windows
95/98 and can backup/restore their own files.

With the rollout of XP, management is planning to
restrict some of the user's current capabilities but,
nonetheless, want the users to continue to have the
ability to backup and restore.

In the laboratory, I have been able to install the
central scheduling service and can backup/restore all
files as an administrator. When I'm logged in as a
power user, it's a different story - I am only able to
backup/restore such System Objects as thr Registry,
COM+ DB, Event Log, Registry, System Files and WMI.

It would appear to be a rights issue. I followed the
procedure put forth in the Tivoli document, "TSM for
Windows, BA Clients Installation & Users Guide":
Considerations for NT, 2000, and XP Client Services
(pp 25-26)

"The account must also have the following permissions
to the HKEY_LOCAL_MACHINE, HKEY_KEY_USERS, and
HKEY_CURRENT_USER registry hives:

Query Value
Set Value
Create Subkey
Enumerate Subkeys"

I put this question to Tivoli Support who suggested
that Windows XP has a Unix-like SU capability that
could be invoked but this isn't even a workaround ,
let alone a solution.

The idea of using the user name as a nodename option
in the dsm.opt file has been discussed but is highly
impractical because some 1500+ users have a user name
in this format:

John[space}Smith.

TSM doesn't like the [space] in a node name.

Again, any ideas is much appreciated.

__
Post your ad for free now! http://personals.yahoo.ca