Print migrator 3.1 Scripting Backups

[Brian]

I'm trying to use Print Migrator 3.1 to backup 3 print
servers with over 300 total printer queues. I've used an
older version to Migrate from NT 4.0 to Windows 2000 a
few years ago and had good succuess. The problem I'm
having is this: If I setup a scheduled job to run under
my domain admin account the backup runs fine. If I use
the AT command to setup the scheduled job the job will
start, but continues to run and never creates the .cab
file...it also runs the CPU from 75% to 100% until I run
Tlist and kill the process. I've tried to set it up
under a backup domain account that has backup operator,
server operator and print operator privileges but it
didn't run...showed it had ran but it never did. Once I
get this working on the local print servers I have to
implement this company wide to over 50 remote servers.
Any suggestions on how to automate this without
specifying my domain account or another domain
adiminsitrator account would greatly be appreaciated.
Thanks

Brian

 

[Nik]

I think your problem is related to the automation process. I think you have
a driver issue when you are restoring the printqueues. Probably you have
some old NT4 printdrivers installed. Does Print Migrator work without using
scheduled tasks?.

We have resently moved 3000 printqueues on 6 printservers from w2k til w2k3
using Print migrator, a *.bat file and scheduled task.
printmig -r \\backupserver\printserver.cab \\printserver


/nik

 

[Brian]

I'm not trying to do a restore of the printer queues,
just a backup in case I lose a print server. I'm also
running a *.bat file and scheduled task.
printmig -b etc. The problem is that I have to run it
under an administrative account for it to work...big
security issue with this one. What permissions does the
account have that you were using for the restore?

Brian

 

[Nik]

It was a administrative account. All information is located på the
systemdrive, so you'll need a administrative account to access the registry
and sysvol if you not explicit have added a another account with elevated
rights or you have shared the sysvol...

/nik

 

[Guest]

Yes that's what I was afraid of. Granting an account
full admin rights on the server just to backup printer
queues is taking a risk...if this account was compromised
then the program or hacker would have full reign on all
the servers. Thanks for your input.

Brian

 

[Nik]

Well...You could schedule a locale job on the server with the local admin
account and point to another server/client for backup location of the *.cap
file

/nik
Yes that's what I was afraid of. Granting an account
full admin rights on the server just to backup printer
queues is taking a risk...if this account was compromised
then the program or hacker would have full reign on all
the servers. Thanks for your input.

Brian