Tuesday, May 29, 2012

TO fix the SMS client GUID issue


How to fix the SMS client GUID issue
1.If the client status unknown in the SMS console after installing the SMS client (make sure that CCM setup.log shows the succeeded message)
2.Use the psexec tool to login to the machine locally
Usage of the tool
Psexec \\IPadress of the machine (space) cmd
Make sure that open client id manager startup.log in the client system to observer the changes
Patch of the client id manager startup.log would be c:\windows\system32\ccm\logs\
Below are the commands you should execute in the PSEXEC tool
a)      net stop ccmexec
b)      del "%windir%\Smscfg.ini"
c)       net start ccmexec
now open “client id manager startup.log “ in client system and observe the message

Once you identify that you fixed the client guid , open the sql and check the system status after few minits .



Use below query to check the same.

SELECT     Name0 AS [Machine Name], User_Name0 AS [User Name],AD_site_name0 as [AD site code] ,creation_date0 as [AD discoverd date],

                      CASE Active0 WHEN '0' THEN 'InActive' WHEN '1' THEN 'Active' ELSE 'Unknown' END AS [Active Client],

                      CASE Client0 WHEN '0' THEN 'No' WHEN '1' THEN 'Yes' ELSE 'Unknown' END AS [Client Status],

                      CASE obsolete0 WHEN '0' THEN 'No' WHEN '1' THEN 'Yes' ELSE 'Unknown' END AS [Obsolete Client], DATEDIFF(D,V_GS_WORKSTATION_STATUS.LASTHWSCAN,GETDATE()) AS [HW SCAN DIFFERENCE]
FROM         v_R_System  LEFT JOIN V_GS_WORKSTATION_STATUS ON V_R_SYSTEM.RESOURCEID = V_GS_WORKSTATION_STATUS.RESOURCEID

WHERE     (Name0 IN (
'Systemanem'))

ConfigMgr 2012- Interesting


ConfigMgr 2012 “How do I?” video series


 http://bit.ly/ytUxU0


Friday, May 25, 2012

SMS/SCCM Sql required query for Daily administration

 SQL Query useful for daily administration

http://sms2003-sccm2007.blogspot.in/2008/08/all-sql-queries.html 

Dcomcnfg - DCOM Settings


Type in the Run command -  “Dcomcnfg”

Go to computer properties and go to the “Com security “ edit limits in both accordingly ( just add your login id and your system name and give all the permissions for you and your computer)

this is required incase you unable to connect to SMS console from XP machine

SMS/SCCM Client Install Script automation



1. Create a folder anywhere in same domain and copy the ccmsetup.exe and psexec.exe to the folder.
2. Create a text file with name computers.txt under C:\ and enter the system names one by one where you wanted to install the SMS Client.
3. Copy the below script and name it as SCCMClientInstall.vbs
4. Double click the file.
5. Enter the Path of the folder that you created in the first step and click ok.
6. Enter the Management Point Name in the next input box. (You can mention any MP name)
7. Check the ccmsetup.log in one machine to verify the client install.


Thursday, May 24, 2012

IP Addressing:


IP Addressing:

There are two versions of IPs

1. IP version 4: offers IPs up to 4.2 billion (32 bit size)
2. IP version 6: 128 bit size.

IP address is used for identifying the system and provides communication.
IP address is of 32 bits divided in four octets.
Each Octet is of 8 bits, separated by a (.) dot.
IP is a combination of Network ID & Host ID.
Uses subnet mask to differentiate Network ID with Host ID.
Subnet mask acts like a mask between Network ID & the Host ID.
Numbers range between 0-255.

Organizations responsible for assigning IPs to clients.

IANA: Internet Assign Naming Authority.
ICANN: Internet Corporation assigning for name Numbers.


IANA has classified IP addressing into classes.

Class A:        1-126(used in LAN/WAN)
Class B:        128 – 191(used in LAN/WAN)
Class C:        192 – 223(used in LAN/WAN)
Class D:        224 – 239 (used for multi casting)
Class E:         240 – 254 (used for experimentation & research)


Class
Format
No of N/Ws
No of Hosts
Subnet mask
Range
A
N.H.H.H
  28-1   126    
224 – 2 16.777.214
255.0.0.0
1 – 126
B
N.N.H.H
216-2  16.384
216 – 2 65.534
255.255.0.0
128 - 191
C
N.N.N.H
224-3  2.097.152
28 – 2   254
255.255.255.0
192 – 223
D
MULTICAST
N/A
N/A
N/A
224 – 239
E
RESEARCH
N/A
N/A
N/A
240 - 254

Class A:The first octet is reserved for network ID.
The first bit of first octet is always (0).

Class B: The first two octets are reserved for Network IDs.
The first two bits of first octet are reserved as (10)

Class C: The first three octets are reserved as network portions.
The first three bits of first octet are reserved as (110)

Class D: Used for Multicasting.
The first four bits of first octet are reserved as (1110)

Class D: Used for Experimentation.
The first four bits of first octet are reserved as (1111)

The first bit of first octet is called as priority bit which determines the class of N/W

0.0.0.0. Are reserved as N/W ID.
255.255.255.255 is reserved as broadcast ID.
127.0.0.1 Is reserved as loop back ID

Implementing/Configuring TCP/IP.

On Desktop
Right click on my network places-properties
Double click local area network-Select properties
Click-Use the following ip address
Specify the address in the box
DNS also same as IP address.

Verifying:

Go to command prompt
Type” ping IP address”. (PING: Packet Internet Groper)

To Increase SMS Client CacheSize


On Error Resume Next

Dim oUIResManager
Dim oCache
Dim CacheSize

CacheSize=3086

Set oUIResManager = createobject("UIResource.UIResourceMgr")

If oUIResManager Is Nothing Then
    wscript.echo "Could not create Resource Manager - quitting"
    wscript.quit
End If

Set oCache=oUIResManager.GetCacheInfo()

If oCache Is Nothing Then
    Set oUIResManager=Nothing
    wscript.echo "Could not get cache info - quitting"
    wscript.quit
End If

oCache.TotalSize=CacheSize

To uninstall using product code - Any app


To uninstall using product code (you can uninstall multiple apps at one go) - use product cod​e.txt and make sure that product code in the text file


-------------------------------------

On error resume next



Dim WSHShell, objFSO, strParentFldr, strProdFile,objTemp,strLine , strRegKey, strSubKey, strUninstallString, exitcode

Set WSHShell = CreateObject("WScript.Shell")

Set objFSO =CreateObject("Scripting.FileSystemObject")

strParentFldr = objFSO.GetParentFolderName(wscript.ScriptFullName)

strProdFile = strParentFldr &"\ProductCode.txt"

Set objTemp = objFSO.OpenTextFile (strProdFile, 1, True)



strSubKey = ""



Do while Not objTemp.AtEndOfStream

                strLine = objTemp.ReadLine

                strRegKey = "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\"& strLine & "\"

                strSubKey = WSHShell.RegRead (strRegkey& "DisplayName")

                if strSubKey <> "" Then

                                strUninstallString ="msiexec /x" & " " & strLine & " /qn"

                                exitcode =WSHShell.Run(strUninstallString, 1, True)

                End IF

                strSubKey = ""

Loop

Wscript.quit (exitcode)


Troubleshooting Management Point Communication


Do you know/why the MP list and MP cert commands : Troubleshooting Management Point Communication

SCCM: How to Exclude Files From Software Inventory



How to Exclude Files From Software Inventory


You can create a hidden file named Skpswi.dat and place it in the root of a client hard drive to exclude it from software inventory. You can also place this file in the root of any folder structure you want to exclude from software inventory. This procedure can be used to disable software inventory on a single workstation or server client, such as a large file server.
The Skpswi.dat file only prevents software inventory for computer clients and does not affect mobile device client inventory.

Software inventory will not inventory the client drive again unless this file is deleted from the drive on the client computer.
To exclude files from software inventory
  1. Using Notepad.exe, create an empty file named SkpSwi.dat.
  2. Right click the SkpSwi.dat file and click properties. In the file properties for the SkpSwi.dat file, select the Hidden attribute.
  3. Place the SkpSwi.dat file at the root of each client hard drive that you do not want to collect software inventory from.

Monday, March 26, 2012

Tip: how can I target applications to specific hardware (just a tip ignore if you know this pls)

Tip: how can I target applications to specific hardware (just a tip ignore if you know this pls)





also you can use below query if you want to create a collection based on hardware:

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.Model in ("Latitude D420","Latitude D630","Latitude D430","Latitude D620")



Note: you can change hardware models based on your requirement in the query.

To increase log file size on SMS/SCCM client: ConfigMgr : Verbose and Debug Logging

To increase log file size:  ConfigMgr : Verbose and Debug Logging

64 Bit machine:
============
1.       In registry, go to HKLM > Software > WOW6432Node > Microsoft > CCM > Logging > @Global
2.       Right click on @Global and click on Permissions. Grant Administrators group with Full control.
3.       Modify the key: “LogLevel” and set the value from 1 to 0 –{This enables Verbose logging}
4.       Now, right click on Logging and create a new key and name it: DebugLogging
5.       Under DebugLogging, create a new string named: "Enabled" ->{Without Quotes}, and set the value to "True" ->{Without Quotes}. –{This enables Debug Logging}

32 Bit machine:
===========
1.       In registry, go to HKLM > Software > Microsoft > CCM > Logging > @Global
2.       Right click on @Global and click on Permissions. Grant Administrators group with Full control.
3.       Modify the key: “LogLevel” and set the value from 1 to 0 –{This enables Verbose logging}
4.       Now, right click on Logging and create a new key and name it: DebugLogging
5.       Under DebugLogging, create a new string named: "Enabled" ->{Without Quotes}, and set the value to "True" ->{Without Quotes}. –{This enables Debug Logging}


Once done restart the SMS AGENT host Service and wait for 10

SCCM to Tanium

SCCM transition Options: of course intune otherwise  Deployment, Patching - Tanium Image - Tazier Inventory - Tanium Remote Control - Zoom  ...