I do _not_ run Citrix. However, I had the same problem on a server whose
systemdisk was D:. One of the 4 start up files (boot.ini, ntldr, etc.) was
missing. Installing the missing file allows the backup of the
systemobjects.
I think the missing file is displayed by NT's backup utility.
On Wed
>I believe you are suffering from a known defect identified by IC32636.
>This apar describes a problem with the client having problems
>backing system files if the root drive is other than C:.
>Per your note below, it appears the boot drive is M:. This is why
>the client works fine if you don't in
I haven't looked into the 5.x clients yet, as my server is still at 4.1.4
and will be for awhile until some old clients go away.
Does the 5.1 client work with a 4.1 server?
Also, can I assume the fix will be applied to the 4.2 client as well?
Thanks... Ken
Rejean
T> cc:
Sent by: Subject: Re: 4.2.1.32 problem with
systemobject on Citrix
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>
Join the club. I have been working with Tivoli for a couple of months
on this (even though they don't support Citrix). They had me upgrade to
4.2.1.30. There thinking is that it has to do with the CAD starting
scheduler. When I stopped using managed services it stopped hitting my TSM
serve
Hello Ken,
I believe you are suffering from a known defect identified by IC32636.
This apar describes a problem with the client having problems
backing system files if the root drive is other than C:.
Per your note below, it appears the boot drive is M:. This is why
the client works fine if you do
