Solved

Logon Scripts not running on 2012 r2 Domain

Posted on 2014-04-01
3
4,071 Views
Last Modified: 2014-04-03
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
0
Comment
Question by:YellowbusTeam
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 13

Assisted Solution

by:Santosh Gupta
Santosh Gupta earned 200 total points
ID: 39968983
Hi,

1. see the event log of any desktop for any policy related error.
2. run RSOP.MSC on effected desktop.
0
 
LVL 58

Accepted Solution

by:
Cliff Galiher earned 300 total points
ID: 39970847
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
 

Author Comment

by:YellowbusTeam
ID: 39974408
Hi we have gone down the route of using Group policy, i will distribute the points now
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently, Microsoft released a best-practice guide for securing Active Directory. It's a whopping 300+ pages long. Those of us tasked with securing our company’s databases and systems would, ideally, have time to devote to learning the ins and outs…
Auditing domain password hashes is a commonly overlooked but critical requirement to ensuring secure passwords practices are followed. Methods exist to extract hashes directly for a live domain however this article describes a process to extract u…
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
This video shows how to use Hyena, from SystemTools Software, to update 100 user accounts from an external text file. View in 1080p for best video quality.

615 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question