I am trying to use the printmig.exe tool to migrate printers from windows server to samba server.
this is what I did:
1. I ran printmig.exe on the windows server.
2. Backed up the printers on the windows servers to a cab file.
3. Tried to restore the printers to the sambashare by specifying the target as //sambaShare.
But I get the following error:
2006:01:25 15:35:38 Access Granted to: \\sambaShare
2006:01:25 15:35:38 Couldn't start the target spooler
2006:01:25 15:35:38 Remote Tree View Failed
Do I need some specila config in smb.conf?
In smb.conf I have a addprinter command.
I also added [admin$] section in the smb.conf file and set enable asu support = no

The problem is more lack of documentation. The spooler
service (internal to smbd) has an associated security
that only allows members of BUILTIN\Administrators
tro start/stop the spooler service. I recently changed
smbd to add the Administrators to anyone that had the
'Domain Admins' sid in their NT token. I can send you
that patch but it will only help in domain or ads mode.
If you have a standalone server, then you must either be root
or create a groupmapping for the Administrators SID and be
a member of that group.
I'll follow up the rest of this thread over email.

(In reply to comment #1)
> The problem is more lack of documentation. The spooler
> service (internal to smbd) has an associated security
> that only allows members of BUILTIN\Administrators
> tro start/stop the spooler service. I recently changed
> smbd to add the Administrators to anyone that had the
> 'Domain Admins' sid in their NT token. I can send you
> that patch but it will only help in domain or ads mode.
>
> If you have a standalone server, then you must either be root
> or create a groupmapping for the Administrators SID and be
> a member of that group.
>
> I'll follow up the rest of this thread over email.
>
After applying the patches suggested I can migrate the print queues but not the drivers.

(In reply to comment #4)
> Are the driver files actually present in the original
> *.cab file? This appears to be a random bug in the
> printmig.exe tool itself.
>
Yes the driver files are present in the cab file.