Jump to content

Recommended Posts

Posted

Me again!

 

Today I'm having a real hair pulling issue. I feel like I've put everything in the correct place but the system still won't pull together.

 

Basically, I want to install TightVNC across our network using a start-up script via GPO. I had followed This Guide from FN-GM word for word and it still just doesn't work!

 

I have:

Created a share @ \\servername\Software$\GPO Applications\TightVNC where domain computers have access to read and execute.

Installed TightVNC to a test machine, set up the settings I would like and exported the registry to the above share.

Put the .msi installer into the above share.

Copied the script in the link above, replacing their locations with ours and saving it as a .bat into the above share.

Put the script into a GPO applied to the OU containing my test machines.

gpupdate /force on the test machines and reboot multiple times to pull the software.

 

And what happens? Diddly squat.

I'm so confused right now it hurts - Any feedback is greatly appreciated.

Posted
If you are looged on as an admin to a machine, browse to the script and run it, does it install?

Yes the Script will install the software and the Reg preferences when ran from an Admin account.

 

Have you tried deploying the msi as a Software Installation in the GPO, ensure that works first and then try deploying the reg key (either as a .bat or through GPP).

I've tried the MSI as a software install via the GPO and I still get nothing.

Posted
Where has the .msi come from ?

Currently using a .exe with the script mentioned, however the .msi I was trying earlier via Software Install in the GPO was direct from the tightvnc.vom website

Posted
So you're running an .msi or an .exe from the server share ?

 

Sounds like permissions to me

I've tried both - MSI through the Software Deployment in GPO and .exe through a startup Script in GPO (not at the same time obviously).

 

The folder security has Domain Computers set to read and execute so I don't get why it would be a permissions issue - although I agree that's what it looks like.

Posted
try making startup script visible on one pc and link it to a copy of the script with a pause in it see if that helps
Posted

Have you done a rsop.msc to check the error ?

 

Have you hit the 'Replace child permission for parent' on the share.

 

(You've probably done this but...) Have you checked the perms on the Share as well as the folder containing the files ?

 

The error log will tell u tho'

Posted
Have you done a rsop.msc to check the error ?
Not sure what this is supposed to show me? The policy is displayed in there yes - am I missing something?

 

Have you hit the 'Replace child permission for parent' on the share.
Yep - No difference

 

(You've probably done this but...) Have you checked the perms on the Share as well as the folder containing the files ?
Yep done that too

 

The error log will tell u tho'
I swear someone is messing with me today because there is literally nothing in the event viewer. Like - am I going crazy?!
Posted
Not sure what this is supposed to show me? The policy is displayed in there yes - am I missing something?

 

Run 'rsop.msc' on the client PC

 

Right click 'Computer Configuration' ---> Properties

 

Look at the 'Error information' for that GPO - it'll tell you whether its tried to process the GPO first of all and whether it failed - Is the policy trying to run?

 

Definitely got the script in 'Computer Configuration' and not 'User Configuration' ?

 

 

Can't think of anything else it would be unless the .msi is corrupt but if you've run it manually, it isnt

 

o

  • Thanks 1
Posted (edited)
Run 'rsop.msc' on the client PC

 

Right click 'Computer Configuration' ---> Properties

 

Look at the 'Error information' for that GPO - it'll tell you whether its tried to process the GPO first of all and whether it failed - Is the policy trying to run?

 

Definitely got the script in 'Computer Configuration' and not 'User Configuration' ?

 

 

Can't think of anything else it would be unless the .msi is corrupt but if you've run it manually, it isnt

 

o

Login Scripts (along with other GPO's applied) is marked with success.

 

Script is 100% in Computer Configuration - I've been that daft before so learnt from that one.

 

It's been a long time since something so straight forward has baffled me so hard. Genuinely stumped.

 

Thanks for your help by the way - I appreciate this is straightforward for most, but I'm just so confused with why it's not working.

Edited by NerdNamedMatt
Posted

I was always leery of installing VNC on client machines; especially seeing as how a lot of those machines were laptops there are frequently taken offsite. I wound up writing a custom launcher for TightVNC that would:

 

  1. Copy TightVNC to the target computer via the admin share
  2. Randomly generate a password for that session
  3. Create the registry keys on the target machine
  4. Register TightVNC as a service and start it
  5. Start the TightVNC client and connect to the target
  6. Wait for the client to be closed on your end and then clean up the registry and files on the targer computer
  7. If the connection was severed then there would be a cleanup script in place to remove all of that stuff on the next boot

 

Requirements are:

  • Open the VNC port on the targets firewall
  • Have the remote registry service running on the target
  • That you have local admin on the target
  • That file sharing is enabled on the target so you have access to the admin share
  • Remote management is enabled
  • A GPO tweak to enable CTRL-ALT-DEL sequences to be sent to the client to logon if need be

 

I can dig out the source if you're interested. I should probably make blog post for it.

Posted
You might want to try using the "Always wait for network at logon" GPO setting as well to make sure the computer waits for a network connection processes policies and scripts etc.
Posted
Post your script up m8

I'm about to kiss you!

 

Pasted my script in here and instantly noticed something. In the script I was pointing it at an admin share rather than the public version of the same folder.

 

Someone get me a beer!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...