Wednesday, October 13, 2010

Windows 2008 IIS Common Issue on MP : Make sure you need to meet this settings on your windows 2008 server

image

 

Windows 2008 IIS Common Issue on MP : Make sure you need to meet this settings on your windows 2008 server

Last hardware inventory 14 days

---------------------------------------------
select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.Name not in (select SMS_R_System.Name from SMS_R_System inner join SMS_G_System_WORKSTATION_STATUS on SMS_G_System_WORKSTATION_STATUS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_WORKSTATION_STATUS.LastHardwareScan >= DateAdd(dd,-14,GetDate()) )
-----------------------

Collections: query to check for obsolete clients

 

 

select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System where obsolete = 1

Monday, October 11, 2010

You must know these collections as handy : Collections End to End

1.Client all system collection

2.Non client systems

3.Inactive systems

4.Obsolete system

5.Duplicate client Yes or No

6. Last hardware inventory 14 days

7.Last software inventory 14 days

8.Last Data discovery cycle.

9. XYZ package, XYZ Advertisement success systems’ collection

10. XYZ package, XYZ Advertisement Failed systems’ collection

11.XYZ subnet collection system

12.Add XYZ system’s to a collection of Existing

13. All SMS server system collection

14. All windows server, workstation,DP,BDP collection

15. All system’s with AD site based

16. Collection limiting to sub collection, linking

17.System’s are in “A” collection But not in “B” Collection & Vice versa

18. In collection “XYZ” Software installed system

19. In collection “XYZ” File inventory(s\w inventory based) installed system

20. In collection “XYZ” file specific method(H\w inventory based) system

21.XYZ patch Installed & Not Installed system

22. All windows update Agent version 7.6 below

23.XYZ user/group collection

Wednesday, October 6, 2010

“The network path was not found" error on Win XP sp3”

The problem
You are unable to connect to any network resource (network shares, printer, etc) on a Windows XP machine, from a Win XP client.
A solution (there could be several causes)

  • On the target machine (the one you're trying to connect to) open up Services, under Administrative Tools in the Start Menu.
  • Scroll down to the Computer Browser service.
  • If it is Disabled or set to Manual, set it to Automatic.
  • Then start it. It may stop immediately again, but this is OK.
  • At this point try to connect to the target machine.
If it still doesn't work, you can try the following:
  • open up Network Connections, under Control Panel.
  • Right click on your network adapter and click on Properties.
  • Click on Internet Protocol (TCP/IP), then click on Properties.
  • Click on Advanced, and click on the WINS tab.
  • Even if it is set to Default, set the radio button to Enable NetBIOS over TCP/IP.
  • Press OK on each screen until everything's closed.
  • Go back to the client machine and try again.
  • You should be able to connect!
If it still doesn't work:
  • Go back to the Services window and find the service named Routing and Remote Access.
  • Double-click on it, set it to Manual, and stop it.
  • Close Services and try to connect from your client machine again.

Tuesday, October 5, 2010

WSUS Wiki and troubleshooting WSUS

Read here on the WSUS Team Blog a nice article about troubleshooting WSUS. It references the site http://www.wsuswiki.com/.

This site was created to provide a place for the WSUS community to share information about WSUS, including troubleshooting steps and best practices. The advantages that this site provides over public news groups include:

  • Content on this site is edited and kept up-to-date. News group postings can get out of date, can contain incorrect information, and are often not corrected.
  • It is easier for readers to find information on this site than in the news group.
  • This site captures minor contribution from many users and both aggregates and persists them over time. This body of work grows and gets better over time whereas newsgroups just grow.
  • It is fun to edit pages and improve on contributions of others. You can not really do that with news groups.

It also references several troubleshooting tips for successful configuration of WSUS.

Check it out.