Logon Scripts not running on 2012 r2 Domain

Hi all,

I have just setup a server2012 domain and i am having issues getting the logon scripts to run via AD in the profile tab and getting the Home folder to connect to a share i have setup.

I have tried various GPO settings regarding slow link speeds etc and they dont work and i have run the script on the PCs just to make sure the script is not wrong.

I have setup logon script via GPO and this works but this is not how i want to set it up.

So any advice you can give that would be great.

Thanks Matt
YellowbusTeamAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Santosh GuptaCommented:
Hi,

1. see the event log of any desktop for any policy related error.
2. run RSOP.MSC on effected desktop.
0
Cliff GaliherCommented:
The script option on the profile tab in AD is considered legacy (like NT4 legacy) and is there for backwards compatibility. I know you say you don't want to use GPOs, but that is the proper way moving foward. You certainly shouldn't be doing new deployments with the legacy option.

So my first question is *why* don't you want to use GPOs? If we understand the underlying reason, we can provide better solutions.

As far as why the script isn't working, all I can say is as a legacy-only option, it is extremely limited. It won't run WSH or Powershell by default, for example. Only old-school batch files. And because of when it is processed (compared to the much more full-featured group policy client), permissions on the file location can be extremely touchy as well. It is possible it isn't running because the machine doesn't have permissions to access the script during the time it is processing the logon, thus a generic "access denied" type of problem.

Both of the above are easily circumvented with group policy, and is the recommended way to do new script needs for the indefinite future.

-Cliff
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
YellowbusTeamAuthor Commented:
Hi we have gone down the route of using Group policy, i will distribute the points now
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.