Moe,
Dantz has verified that there is a bug in the firmware of the Yamaha 6416
CD-RW drive. While we have notified Yamaha of this bug, until Yamaha
releases a fix for this problem, we can no longer officially support backup
to the Yamaha 6416 CD-RW drive with Retrospect or Retrospect Express.
Dean,
Retrospect for Mac client packs will work with Retrospect for Windows. Old
Windows activator codes become license codes with Retrospect 5.0 Windows (as
well as Retrospect 4.2 Macintosh).
If you have further questions, please call us directly. Our technical
support number is 925.253.3050,
Dean,
Can you run Microsoft's built-in registry copy utility? This has generally
better error reporting and may give you some more insight into what may be
going wrong. It's pretty much the same as Regcopy anyway, except that I
believe you can't schedule it, as you can with our Registry Backup
Oh, also:
If anyone's running an older version of the Windows client (pre-5.0), you
want to make sure the Registry Backup Manager is v1.3. Older versions of the
RBM didn't have as good error reporting as the latest version, and also had
problems backing up the default user.
Matthew Tevenan
All,
I've some references to DHCP but nothing that answers my question. Currently part of
our network is on a 144.118.xx.xx IP address scheme. We're converting over to a
129.25.xx.xx address scheme. Currently all the machines being backed up have static
IP addresses. However some of them
Ryan,
Unfortunately you will have to log out each and every client and then log
them back in via multicast or subnet broadcast. Retrospect Mac doesn't have
the capability to change the way you access a client automatically.
While Retrospect for Windows does have this capability (click the
Ryan,
By the way, I'm assuming you've originally added all of these clients by
address (since you made a point of mentioning they all had static
addresses).
If not, the rules change. If you add a subnet to 4.2 and the clients were
initially added via default multicast, Retrospect will look for
I feel awfully silly for not noticing this sooner, but
regcopy is leaving a record of the failure in the system event log.
It finds a user profile mentioned in the registry that no longer
lives on the local disk. I removed this profile pointer from the
registry and the problem went
