This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problem - Protecting clients

Hello,

I am doing this for educational purposes only.

My problem is that my workstation will not be protected by SEC server. When I am discovering the AD for computers, it will find my one and only workstation named "DEOCL1". This workstation is greyed, and my own computer in SEC is coloured.

When I click on Protect, everything goes well until it returns with an Error; The computer can no longer be contacted. It may have been shut down, renamed or disconnected, or a required service may not be running. It may be running Windows XP Home.

My current situation;

ESXi 4.1 with running the following;

Server: Windows Server 2008 R2

Client: Windows 7 Pro

Domain name: testdomain.local

Client name: DEOCL1.testdomain.local

Client is able to access \\192.168.1.102\c$ ( which 192.168.1.102 is the Server ip ( SEC Server ))

All configurations in this topic have been successfully applied to the domain network with gpupdate /force.

Client firewall has been turned off, server firewall is on.

Can anybody help me?

This thread was automatically locked due to age.

0 jak over 14 years ago

Hi,

Using the client machine name as it appears in SEC, i.e. the NetBIOS name and from the SEC server, as logged in as the account you are using in the deployment wizard, can you connect to:

\\NetBIOSNameOfClient\C$\windows\tasks\

and create a file/task?

Does the management service of SEC manage to create the job file on the client but then it doesn't run or is it never created?

Does this affect all Windows 7 machines you have or do some work?

There is definitely a distinction between creating the task and it not running or not creating the task at all.

Regards,

Jak
:7153
Cancel
Vote Up 0 Vote Down

Cancel