Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Network client-server identity problem - on the network but not properly recognised

Posted on 2011-10-09
15
Medium Priority
?
394 Views
Last Modified: 2012-05-12
I have upgraded an XP x32 machine to Windows7 and everything seemed fine. But it isn't.

The machine has IP 10.X.Y.200 and the server has IP 10.X.Y.100. The client is present as a managed computer in the server management console.

However, the client is not recognised in Symantec Protection Centre and is unable to identify any network printers.

It can reach the internet and mail is fine.

The odd thing is that until about a week ago everything was fine and the client was recognised in SPC and could print.

The only thing that has changed in a new graphics card has been installed.

When I look at the event logs I see no print related errors. The only error I seem to get is a group policy one (copy of error message attached). All other Windows7 clients are recognised by SPC and can print to the network printers.

Finally, I can use mstsc.exe from all the clients EXCEPT the one I have print and SPC problems with.

Any advice gratefully received. WMI-error.txt
0
Comment
Question by:MarcusN
  • 8
  • 7
15 Comments
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 36942618
well since you can't technically upgrade xp to Win7 you did a clean install, correct?
What version of SBS are you running?
How did you join the new Windows 7 computer to the domain?
0
 

Author Comment

by:MarcusN
ID: 36942716
You're right, sorry for my loose language.

I performed a clean install of Windows7 x64 onto the xw8200 workstation that had previously been running XP x32.

After installation the xw8200 was in a Workgroup. I logged on as a local administrator and changed the Computer->Properties->Name and Domain Settings to add it to the domain controlled by the SBS 2003 R2 Domain Controller. That worked fine. (The xw8200 NIC MAC address has a DHCP lease reservation on the SBS 2003 R2 so the MAC was recognised and the computer, toghether with the change in meta data appeared correctly in the Server Management Console listing of Computers. It still does.)

I reinstalled all the programmes and, where I needed to get x64 applications, bought all the new softweare and installed that.

In fact, everything worked perectly (with the exception of WSUS for which I hae a currently open question).

The on or about the 29th September, coinciding with the change of the graphics card, the xw8200 stopped being managed by Symantec Protection Centre (which works with all the other Windows7 computers on the network) and I can no longer mstsc /v:SBSSERVERNAME /admin or print to a network printer.

Is there any way I can "repair" the Windows7 installation like I could do in the past with XP (from the Control Panel->Add/Remove Programs etc etc)?

What should I do to the registry to get more event log data as I don't think I am currently capturing the events that are resulting from theproblem?

0
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 36943609
Two things
The Windows 7 machine was not joined to the SBS domain using the proper method...the ConnectComputer Utility does much more than just joining the domain.

Second..what happens if you remove the video card and removed the Video Card Software?
0
Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

 

Author Comment

by:MarcusN
ID: 36943667
The problem appears to be soething to do with group policies. I've put the output from the event log with this reply.

I'm going to remove the computer from the domain and then, from the SBS 2003 use the connect computer utility. What's the best way to do that?

I can't remove the video card as there is no on-board video on the xw8200 mobo and I no longer have the card that was there before. GPerrors-2011-10-10.txt
0
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 36943733
before I suggest how to add to the domain
You may wish to save the profile or you may issues with apps working
Do you have other Windows 7 machines in the domain?  How where they joined?
0
 

Author Comment

by:MarcusN
ID: 36943886
The network has over 20 Windows7 clients. They were added in two ways; either from the server, or sometimes by loging on to the local client as a workgroup administrator, changing the network settings to the domain (using a domain admin for authentication.logon) and rebooting.

It's only the xw8200 that has the problem and it really appears to be something to do with the group policies.
0
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 36943904
If you look in ADUC, what OU is the computer located in?
0
 

Author Comment

by:MarcusN
ID: 36944144
It's in my business -> computers -> SBS computers ... which is where all the other computers on the network are as well (single OU).

Could it be that WMI is corrupt on the client? WMI is automatic and started but the event log carries a WMI error message.

The message relates to GP {8A63E61B-F255-424D-88D7-4D984C213992} ... where do I find that?

0
 
LVL 35

Accepted Solution

by:
Cris Hanna earned 1500 total points
ID: 36944412
Should be able to find it in the registry by searching on that GUID
0
 

Author Comment

by:MarcusN
ID: 36957812
OK, but when I find it, what do I do to it?
0
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 36957979
The solution I would recommend is to disjoin from the domain...you can save the profile if you wish...
Then rejoin to the Windows SBS domain using the connect computer wizard...I would expect it to then go away.
0
 

Author Comment

by:MarcusN
ID: 36958120
OK, is that done at the SBS server? Have you a link with step-by-step instructions that I can follow so I don't make a mess of things?
0
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 36958192
Change the workstation from domain to workgroup (you MUST know the local administrator password for that computer (NOT the Domain Admin password)

Reboot

Log on to the workstation with the local administrator account

Right Click on IE > Run As Administrator

in the address bar type http://sbsservername/connectcomputer (obviously i hope you'll substitute the actual name of your sbs server)

Follow the onscreen prompts

Before doing this...I strongly encourage you to review the following http://support.microsoft.com/kb/926505
0
 

Author Comment

by:MarcusN
ID: 36999451
OK, I have now resolved the problem. It had nothing to do with how the client was joined to the domain.

The xw8200 workstation is a Symantec Endpoint Protection client AND a PCTools Spyware Doctor client. That was fine in XP, but not in Windows7 (you have to delve into GPOs to discover this but I couldn't get the two applications to exist happily together).

The solution was to uninstall Spyware Doctor, reboot and, hey presto, xw8200 is a client in the SBS domain once again.

Thanks for all your help.
0
 

Author Closing Comment

by:MarcusN
ID: 36999460
Problem was an application conflict. Resolved by uninstalling one of the two conflicting AV products.
0

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is in regards to the Cisco QSFP-4SFP10G-CU1M cables, which are designed to uplink/downlink 40GB ports to 10GB SFP ports. I recently experienced this and found very little configuration documentation on how these are supposed to be confi…
This article will show how Aten was able to supply easy management and control for Artear's video walls and wide range display configurations of their newsroom.
If you're a developer or IT admin, you’re probably tasked with managing multiple websites, servers, applications, and levels of security on a daily basis. While this can be extremely time consuming, it can also be frustrating when systems aren't wor…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question