Jump to content

skenmy

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by skenmy

  1. Whereabouts would this switch be? Can't see anything obvious...
  2. Hi all, I have the following script: Set objShell = CreateObject("WScript.Shell") Set objNetwork = CreateObject("WScript.Network") If StrComp(Mid(objNetwork.ComputerName, 1, 4), "I1ZC") = 0 Then objShell.run """C:\Program Files\YouthWire\YWPlatform.exe""" End If Set objNetwork = Nothing Set objShell = Nothing This is assigned to a few OUs. The script is definately executing (as evidenced by a couple of MsgBox calls dabbled throughout the program) and the If statement is definately returning TRUE. The program (YWPlatform.exe) does not execute on logon. However, if I create a shortcut to the script (which resides on SysVol) and execute it under one of our student user accounts (one under the OU that is executing the VBS file), the program runs absolutely fine. One thing I have noticed is that I get a File Security Warning dialog box asking me if I want to Open or Cancel running the VBS file - however this does not pop up when run on logon. Any advice on how to get the program to execute on logon would be most appreciated!
  3. We have started having problems with our Exchange Server authentication (after no apparent changes to our exchange server!) Whereas before the Integrated Authentication worked absolutely fine, users now have to enter their username and password again before they can view OWA internally. I have managed to get this to an acceptable level whereby they do not have to prefix their username with the domain name, but is it possible to regain the old functionality - whereby it would use the Windows logon credentials to authenticate? What could have caused this? I've played with the Authentication settings to no avail... Thanks in advance!
  4. As a quick update, we have solved this issue by using the "Run these programs at user logon" setting in the GPO. We never did get the .bat working...
  5. I have a GPO to run an exe file on a share on one of our servers. The bat file that the GPO should execute looks like this: start \\SERV01\RPM$\client.exe data=\\SERV01\RPM$\Data Just running the script causes the client to start on a local machine, however the GPO does not start the client program. GPO Results shows that the GPO is firing, and I can see no errors in the Event Viewer for the local machine. This one is baffling me! Any ideas?
  6. As for the permissions, they are our "normal", the user and domain admins have full control, and the staff user group have everything bar full control (this is for students, omit the last part for staff users) By default the user is the owner of the home directory. Our structure looks like this: \\sansserver\YearOfEntryData$\StudentNumber So we have a common share per year group, and the home directories are mapped to each individual students' number.
  7. Hi Ben, We do use our groups to redirect, but all the groups have the same policy, to redirect to the users' home directory. Grant exclusive rights is unticked.
  8. Hi all! Got an odd one happening here - we have users (both teachers and students) losing access to their "My Documents" shortcut on the desktop (which is mapped to their network share), seemingly randomly. Double clicking the icon gives a permissions error ("You do not have sufficient privileges to perform this action"). Accessing the same network share through a drive mapping works absolutely fine. There appears to be no correlation in machines, times, or AD groupings. We have an interim solution to the issue - if we add the network user to local power users on any machine and log them on and off again, then remove the local power user access, they regain access to their shortcut throughout the school! Does anyone have any ideas as to what could be happening? We are all baffled here!
  9. You say it has been automatically joined to the domain - are you sure? The simple login screens disappear in Vista when you join to a domain and you get the standard 2-box login with the domain name below it. I suggest removing it from the domain it claims to be connected to (put it into a Workgroup), reboot, and then rejoin it.
×
×
  • Create New...