skeep VNC console

[TomClay]

Hmm, well... that would stop it working if it doesnt exist. Does the attribute still exist in ADSI? ipHostNumber is and Active Directory attribute by standard. There is a list here of the AD attributes. All Attributes (Windows)

 

Which script produced that error?

 

Tom.

Edited February 28, 2013 by TomClay
Additional question

[qUoTuM]

After running your script manually the information is in the ADSI. The error appears when I try to search for the PC in Skeep.

So the only problem now should be the fact that ipHostNumber doesn't exist so the script tries to get information that don't exist and produce that error?.. is it possible that it's not standard in Server 2003?

 

EDIT: Ok, i saw this: http://msdn.microsoft.com/en-us/library/cc220013.aspx

It says that it's only implemented on Server 2003 R2.

Edited February 28, 2013 by qUoTuM

[TomClay]

Do you get an error when running "Local Network Info.VBS"? Because that has no input to ADSI. All that does is collate the information from the computer it is run on in a dialogue box. If there error occurs there then it would be case that it cannot pull the information from the machine. You would atleast then know where the issue was, be it the local computer or AD?

 

What network are you using? If the AD server is 2003 I would presume you dont need the new script but should use the original? I only adapted it for Server 2008 R2, not that I am sure the new one wont work on server 2003? Also what OS are the computers running?

[qUoTuM]

When I run Local Network Info I don't get an error.

The original script doesn't work only your script is working.

The Computers are running Windows 7.

 

I don't know if you understand the screenshot i posted before, but it says that the script can't run because it can't find the ipHostNumber which don't exists.

So in my opinion thats the only problem I have at the moment?

Edited February 28, 2013 by qUoTuM

[TomClay]

Sorry, I miss understood before. ADSI is being updated correctly by the login script but you are receiving the error using skeep. My Mistake.

 

Skeep VNC console - Spiceworks

 

You arent the first with the same error but there isnt a real answer on that page. More a sort of do with out approach. Fingers crossed for ADAM. It does look like the right comment was made in that post "It sounds like Skeep cannot find an Active Directory object computer.". I wouldnt know where to go from here. Perhaps try installing skeep on another PC to rule that out?

 

Tom

[FatBoy]

Some great fault finding posts there Tom I have contacted Skeep him self and he said the ADSchema.vbs is

 

"That is what sets up the permissions in ad. As long as you have permissions already just running the script should work."

 

So maybe this could help with your problem, altho its a long shot. Like you say if that ip attribute is missing it going to throw up all sorts of problems, why wouldn't you have it tho, random?

[TomClay]

I thought that at first then when I re-read the posts, it looks more like ipHostAddress is present in ADSI and the script is updating ADSI. Its the HTA program itself that is failing to read from the AD.

[FatBoy]

Surely it's got to be something to do with permissions then?

[qUoTuM]

I will try something now and I will let you guys know if I was successfully next week.

[tehnewby1]

Hello guys, I am pretty new to IT (was on my last bit of 3 years of schooling before this job) and I just got hired on at a company not 2 weeks ago, well I had an issue with needing to access an employees machine without them knowing on my first full day there and had no way to do it. After some web searching i have found skeep, it seems sweet but i need some help setting it up and getting all the stuff like ip/username searching established. I have never really used vnc and this is my first IT job out of school so im about as green as a pea. Its a windows 7 domain and they have a pre-existing active directory set up, so far skeep has been nice for being able to access the servers this place has. If anyone would be willing to help me out with this and maybe future issues i would be glad to accept the graciousness xD

 

Sincerely,

tehnewby1

[FatBoy]

Hi tehnewby1,

 

Have you read though this whole thread first to see if any of the mentioned solutions fix your issue?

Thanks

FB

[tehnewby1]

FB,

 

I have read quite a bit of it actually lol... the only problem being i am at a near complete loss on most of it due to the fact i have such little experience. All I know is basic stuff, and that i like the promise this software shows.

 

tehnewby1

[TomClay]

Hi Newby,

 

Maybe you should start by telling us what you have done to press, what you have achieved, what you cant do and what you want to do. Then we have some idea of what you need help with.

 

Tom

[tehnewby1]

Tom,

 

Well like I formerly said I haven't been here for long, I'm still getting the "lay of the land" so to speak and am trying to sort out exactly how their servers, software, etc. are all ran and kept up to date/backed up. I need a go to program for network administration and it seems like Skeep could be that program. I would like to be able to access my employees desktops/files and other stuff with ease and without notification if the situation deems it necessary. My main problem is lack of general experience and limited knowledge of the protocols, programs, and processes that this entails (i.e. active directory). I'm not completely clueless and usually pick up on things pretty fast but its good to have some guidance so I know I'm learning the right stuff and I have a support line to call upon in the case of me being completely lost like right now aha.

 

tehnewby1

[FatBoy]

Hi newby,

 

What Tom is saying is that you'll have to tell us at what point of the install/use of skeep your are stuck at? I see the servers are working, is it just that the IP address and usernames aren't against the machine names when you search? Have you put the two scripts (skeeplogon.vbs and skeeplogoff.vbs) into a group policy to run so that they run each time a user logs on or off?

Thanks

FB

[tehnewby1]

FB/Tom,

 

All I have done thus far is install skeep on my computer. It scanned for the servers automatically I s'pose because I never had it do that, they just showed up in the Servers (RDP) box. Yes, that is the next thing I'm trying to get to work now, I have not placed those scripts or anything because I have never set up a group policy before.. besides that I just don't know what im supposed to do with it, like the deploy VNC command and stuff like that. I'm sorry I am not being very helpful to my own cause, this must be aggravating to you and i thank you for your patience with me.

 

Tehnewby1

[FatBoy]

Hi newby,

 

The first thing you need to look into then as assigning the two scripts to run via group policy, run the logon at logon and logoff at logoff for the users! google it, theres lots of people describing different ways of doing it, something like this How to Add VBS to Group Policy Logon - Spiceworks

Thanks

FB

[TomClay]

FB has set you off with the Group Policy. It is a simple User Configuration Logon script and a Logoff Script. (not computer configuration) FB has set you on the right path.

 

So lets start with the main function of the program first. You want to be able to VNC (remotely control) the computers.

 

Firsts things first, Setup the VNC Deployment Settings (UVNC_Settings.exe / Ultravnc.ini)

1. Open Skeep

2. Tools > Settings

Now you are in the settings area were you can setup how you want the VNC Service (which you deploy to all the clients) to work.

3. Security Tab

4. Enter a VNC Password (I only use this password so leave "Required MS Logon" unticked, maybe something you can put some time into after the fundamentals, keep it fairly complex you are stabbing a hole into the whole pc dont forget)

5. Password required, Allow shutdown ultravnc and allow edit clients want to be ticked.

6. Encryption can be used if you want. Again, fundamentally not required.

 

7. Screen Capture

You mentioned you wanted to control the user seemlessly. To do so you are going to need to set a few things here:

Tick these:

Poll Full Screen

Poll Foreground window

Low Accuracy

Use System HookDLL

Use Mirror Driver

Show Primary display.

 

All the rest should be unicked. I found this is the fastest config without disturbing the user.

8. Deploy VNC to a client, preferably a test machine that you can get to easily (IE turning your head left or right 60 degrees).

 

Phew, that is the first bit sorted. Now you need to allow the port on the client machine through the firewall, otherwise you wont get in. 5900 is the default port. Allow all access to the 5900 port to the winVNC.exe application that "Deploy" will install on the remote machine.

 

Now you should be able to at least VNC onto that machine. Have a good play around if it doesnt work. You can always reinstall skeep or uninstall the service if needed. I have a decent CMD script which uninstalls all VNC programs which I will share if its needed.

 

 

You have plenty to chew on for now. Best of luck.

Tom.

[qUoTuM]

Just a little statusupdate of my problems:

 

It's all working fine right now, exept one important thing. When the user is logging in and the script runs over the policy, it says accsess dienied (line 29 character 3). Looking forward to solve the problem!

[tehnewby1]

FB/Tom

 

Thanks a lot so far fellas, in regards to FB,with some help I got the global policy set for the two log in/log off scripts, and now the username when I'm logged in on my computer shows up but no one else... also the IP doesn't show up in its respective column, any thoughts on whats wrong there? Now Tom I did what you said (thanks for the great precise instructions) and I am about to move on to the firewall modification and testing, but i couldn't help but wonder if there is a way to set the firewall thing to group policy aswell or a way to do that in bulk for all machines? Thanks again guys.

 

Tehnewb

[TomClay]

There is indeed a computer policy that will do this. Follow so: Computer Configuration > Policies > Windows Settings > Security Settings > Windows Firewall with Advanced Security > Inbound Rules.

 

Add the service here.

 

Being a computer policy, remember you need to do some computer restarting to apply it. A way of getting more consistent results is to use the GPUPDATE /Force command on the client PC after applying the GPO. Then Restart it.

 

 

As for your login script issue, it may be showing you online because you ran the script manually. Try having someone else run the script manually. You might need to try the script I shared earlier in this thread.

 

Tom.

[tehnewby1]

Tom

 

Alright yeah I found the option in the policy stuff on the domain controller. And well see i actually didn't run teh script manually... with some help i just put it on a GP. I had remote access to my computer then through skeep went into the domain controller, set the policy then logged out and logged into my account. Then i showed up and i had someone else log off and in and they didnt. I may try that new script but also i think i will try that command you mentioned for the firewall. In any case thanks

[qUoTuM]

Just a short question.. was anyone of you guys able to get the menu with the containers on the left side to work?

[TomClay]

QuOtUm -

I had the left work from the off out of the box. See Screenshot attached. Didnt FB say that this was build by the ADSchema.vbs? Something like it sets permissions in the AD and should be run as administrator as a one off. Run as administrator.

 

Newby -

I am totally lost in your post. Sorry. Too many crossed wires for me. Skeep is pretty instant, try this.

1. Run the Logon script on your pc

2. open skeep and see the information is correct for your pc

If yes - run the logoff script on your pc and see if it shows grey (after refreshing skeep)

If no - run the alternative logon script and see if that works (after refreshing skeep)

If that worked try run the logoff script on your pc and see if it shows grey (after refreshing skeep)

 

Then you know what scripts work, dont work and which to put out via GP. You also know that you are getting the right information etc.

Sounds like you are on the right track. Dont confuse the RDP connections to the Servers in the bottom left with the VNC connections to the client PC's in the top left.

 

Tom

[qUoTuM]

Everything is working now, exept the ADScheme.vbs thing..

It was a long way getting this shit to work, haha

First I tried to modify the script and spend 3 whole days with analysis what is working and what doesn't. Waste of time.

 

I documented what I have done so far. It's in german but I will translate it to english when I have time, maybe it will help someone in the future.

 

Short version:

- AD Scheme extension for ipHostNumber which is not included in Windows Server 2003, only in R2.

- Modified the original script with an other IP-Address.

- Changeing the user permissions in the Domain, because they didn't had the permissions to write the information back to the ADSI.

 

Btw. @tehnewby1

Welcome to IT. I just started my apprenticeship 6 months ago so i'm pretty new too

Edited March 12, 2013 by qUoTuM