PDA

View Full Version : Login script weirdness



Stevo
24-Sep-2014, 23:41
Anyone know why a login script (in a.d.) that has worked for months and
months would up and not process completely now?

It's merging a .reg (setting a default printer) entry into the HKCU
portion of the registry, and like I said, it's worked for a long time,
just recently quit working properly.

If I try to merge the .reg into the registry manually, I get an error
"Cannot access the registry".

Weird thing is, if I manually change the default printer, then try to
merge that entry, it works just fine.

--
Stevo

ab
24-Sep-2014, 23:52
\On 09/24/2014 04:41 PM, Stevo wrote:
> Anyone know why a login script (in a.d.) that has worked for months and
> months would up and not process completely now?

Because something changed. What changed?

> It's merging a .reg (setting a default printer) entry into the HKCU
> portion of the registry, and like I said, it's worked for a long time,
> just recently quit working properly.

When what changed?

> If I try to merge the .reg into the registry manually, I get an error
> "Cannot access the registry".

This seems like a good clue. You would seem to lack rights to the
registry. Your user isn't powerful, or UAC is "helping" you, or other
ACLs in the registry are stopping you from being productive.

> Weird thing is, if I manually change the default printer, then try to
> merge that entry, it works just fine.

It is afe to assume that this registry-hacking file plays with printing
somehow? If so, I'm guessing in-registry ACLs are causing you the problem.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

Joseph Marton
25-Sep-2014, 01:14
Stevo wrote:

> Anyone know why a login script (in a.d.) that has worked for months
> and months would up and not process completely now?

Because it's AD? :-)

--
Does this washcloth smell like chloroform?

Stevo
25-Sep-2014, 15:15
ab sounds like they 'said':

> Because something changed. What changed?

Only change was combining two working batch files into one.


> This seems like a good clue. You would seem to lack rights to the
> registry. Your user isn't powerful, or UAC is "helping" you, or other
> ACLs in the registry are stopping you from being productive.

UAC is off, user logging in is a local admin.

> It is afe to assume that this registry-hacking file plays with
> printing somehow? If so, I'm guessing in-registry ACLs are causing
> you the problem.

I'm curious why this would cause a problem for a couple VMs in this
pool, but others work just fine.

--
Stevo

Stevo
25-Sep-2014, 15:16
Joseph Marton sounds like they 'said':

> Because it's AD? :-)

So my response to Joseph's comment is...

That's what I believe

--
Stevo