Print issue on ghosted machines

[ccoverne]

At the beginning of our school year we received a new server. Due to an
error in our AD, we couldn't connect the two servers one being a W2K and
other 2003. We set up a second domain and called it lps.local. I am slowly
migrating all accounts, printers, etc.. to the lps.local domain. We have
machines that were ghosted right before the lps.local was added. I went in
and changed the tcp/ip, wins, and dns settings to be pointed to the .local
and our student accounts can add printers or at least some of them from our
old domain. The machines that were ghosted after the .local was put into
place student accounts can't add a printer. The get a message saying there
is a policy that disallows printers added from that queue. Any suggestions?
I don't know where the problem is in the local security policies on the
machine or with the Policies set on the new server's AD. We are not using
roaming profiles, just mapped drives.

 

[Meinolf Weber]

Re: Print issue on ghosted machines

Hello ccoverne,

If you have created a new domain you have to add the clients to the new domain.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> At the beginning of our school year we received a new server. Due to
> an error in our AD, we couldn't connect the two servers one being a
> W2K and other 2003. We set up a second domain and called it
> lps.local. I am slowly migrating all accounts, printers, etc.. to the
> lps.local domain. We have machines that were ghosted right before the
> lps.local was added. I went in and changed the tcp/ip, wins, and dns
> settings to be pointed to the .local and our student accounts can add
> printers or at least some of them from our old domain. The machines
> that were ghosted after the .local was put into place student accounts
> can't add a printer. The get a message saying there is a policy that
> disallows printers added from that queue. Any suggestions? I don't
> know where the problem is in the local security policies on the
> machine or with the Policies set on the new server's AD. We are not
> using roaming profiles, just mapped drives.
>

 

[ccoverne]

Re: Print issue on ghosted machines

Thanks for the issue but I already added the machines and user accounts to
that domain and that doesn't seem to work.

"Meinolf Weber" wrote:

> Hello ccoverne,
>
> If you have created a new domain you have to add the clients to the new domain.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
>
> > At the beginning of our school year we received a new server. Due to
> > an error in our AD, we couldn't connect the two servers one being a
> > W2K and other 2003. We set up a second domain and called it
> > lps.local. I am slowly migrating all accounts, printers, etc.. to the
> > lps.local domain. We have machines that were ghosted right before the
> > lps.local was added. I went in and changed the tcp/ip, wins, and dns
> > settings to be pointed to the .local and our student accounts can add
> > printers or at least some of them from our old domain. The machines
> > that were ghosted after the .local was put into place student accounts
> > can't add a printer. The get a message saying there is a policy that
> > disallows printers added from that queue. Any suggestions? I don't
> > know where the problem is in the local security policies on the
> > machine or with the Policies set on the new server's AD. We are not
> > using roaming profiles, just mapped drives.
> >
>
>
>