u150 Build: 9.4.2
Hello
Had another crack of finally getting directory connector working and am finally making progress. I had to fix quite a few AD and GP issues, as most of my existing policies were damaged when one of our DC's died a few months back. I confident group policies are now working throughout the domain.
I created a login script GPO, but i had to point it at a .bat file that in turn ran the .vb due to it hanging, a common issue I believe.
But still have a few problems
Unfortunately none of the XP machines are triggering the GPO as far as I can tell, despite all testing suggesting it is.
These pc's are shown with blank information on the untangle and can see no events for them in directory connector.
I can run the script manually and it works, but not at login
I have got round this for the time being by adding a login.bat to the users profile, this does run at login unlike the GPO.
As these few machines are due to be upgraded shortly so so not overly concerned about this
The main problem I have is a number of win7 machines are being picked up on the untangle by a pc name rather than user name. They appear like: PC05$, PC42$ etc
This suggests to me the script is being run for it to be detected by the u150, but its not collecting the correct data for these few machines.
Has anyone encountered this?
I am sure it is most likely an issue with AD in some way, but at the moment haven't got a clue what might cause this on just these few machines when it works ok on all of the 30+ others, I can see nothing that differs.
Again if I manually run the vb script from one of them, it then starts picking up the username correctly?
any suggestions would be welcome
Anyone experienced issues with AV effecting the scripts from being run? I have looked at logs, there are a few events on some pc's, but nothing obvious stands out at the moment.
many thanks
k
Hello
Had another crack of finally getting directory connector working and am finally making progress. I had to fix quite a few AD and GP issues, as most of my existing policies were damaged when one of our DC's died a few months back. I confident group policies are now working throughout the domain.
I created a login script GPO, but i had to point it at a .bat file that in turn ran the .vb due to it hanging, a common issue I believe.
But still have a few problems
Unfortunately none of the XP machines are triggering the GPO as far as I can tell, despite all testing suggesting it is.
These pc's are shown with blank information on the untangle and can see no events for them in directory connector.
I can run the script manually and it works, but not at login
I have got round this for the time being by adding a login.bat to the users profile, this does run at login unlike the GPO.
As these few machines are due to be upgraded shortly so so not overly concerned about this
The main problem I have is a number of win7 machines are being picked up on the untangle by a pc name rather than user name. They appear like: PC05$, PC42$ etc
This suggests to me the script is being run for it to be detected by the u150, but its not collecting the correct data for these few machines.
Has anyone encountered this?
I am sure it is most likely an issue with AD in some way, but at the moment haven't got a clue what might cause this on just these few machines when it works ok on all of the 30+ others, I can see nothing that differs.
Again if I manually run the vb script from one of them, it then starts picking up the username correctly?
any suggestions would be welcome
Anyone experienced issues with AV effecting the scripts from being run? I have looked at logs, there are a few events on some pc's, but nothing obvious stands out at the moment.
many thanks
k