Abhishek Joshi Learning SMS/SCCM/SQL 2005/2008

SMS and SCCM

My last blog on BlogcastRepository.com

This is my last blog on BlogcastRepository.com. I am leaving my old blogs here and moving to the new blog  http://systemsmanagement.spaces.live.com/blog/ .

You will find me in various spaces

 My Old Blog i.e here only.

 My New Blog :http://systemsmanagement.spaces.live.com/blog//  

 My Web Site : http://abhishekjoshi.com/default.aspx

 Technet http://social.technet.microsoft.com/Forums/en-US/user/threads?user=Abhishek.Joshi

Share this post:                                       
List of hotfixes and updates that are contained in System Center Configuration Manager 2007 Service Pack 2
List of hotfixes and updates that are contained in System Center Configuration Manager 2007 Service Pack 2

http://support.microsoft.com/?kbid=971348

Share this post:                                       
Forefront Endpoint Protection (FEP) on System Center Configuration Manager

Based on customer feedback and market trends, Microsoft has made the strategic decision to build Forefront Endpoint Protection (FEP) on System Center Configuration Manager, Microsoft’s solution to comprehensively assess, deploy, and update servers, clients, and devices. 

Please go thorough the link for more details.

Share this post:                                       
Posted: Oct 13 2009, 02:23 AM by Abhishek Joshi | with no comments
Filed under: ,
Got MVP award

I am pleased to share with you that, Today I have been awarded as MVP (Microsoft Most Valuable Professional) for System Center Configuration Manager towards contributing post/blogs in  http://blogcastrepository.com/members/Abhishek.aspx

Thanks to Brian, who has given us http://blogcastrepository.com as platform to explore technical skills.

 

 

Share this post:                                       
Share Files Anywhere You’re Online, 24/7

http://windowslive.com/online/skydrive?ocid=BAN_MSCOM_HPF_WL_SD_01072009

 Store, access, and share your files with friends or co-workers, from anywhere online. Free 25 GB online storage means you can easily get to your stuff with just a few quick clicks

More features

  • Password protection: You set the passwords and you decide who sees what, so you have confidence that your data is in your control.
  • Drag and drop: Uploading content is as easy as dragging and dropping the files from your computer onto the Web.
  • Shared folders: Working on a project with classmates, co-workers, or family? With shared folders, the whole crew can upload, download, and collaborate with you on documents and other files.
  • Direct links: Each folder on SkyDrive has a unique Web address, so you can save the link as a favorite or copy-and-paste it into e-mail or other documents for direct access.

 

Share this post:                                       
Infrastructure Planning and Design Guide Series

The Infrastructure Planning and Design guide series gives you architectural guidance for Microsoft infrastructure products. The IPD guides help clarify and streamline design processes for Microsoft infrastructure technologies, with each guide addressing a unique infrastructure technology or scenario

http://technet.microsoft.com/en-us/solutionaccelerators/dd408383.aspx

You will also find IPD for SCCM.

 

Share this post:                                       
Distribution point fact -1 - Determine which NTFS drive should have distribution point

First time when you distribute the pkg to distribution point then SMS/SCCM chooses the NTFS drive which has maximum free space.If you have 2 to 3 NTFS drives and you want to chosse one of them;then there is no provision given at SMS/SCCM server side. Create the text file on the other drives with the name NO_SMS_ON_DRIVE.SMS which will prevent respective NTFS drive from creating SMSPKG<drive letter> folder.Drive which dont has  NO_SMS_ON_DRIVE.SMS file,will have SMSPKG<drive letter> folder.If you want more information then search on google with NO_SMS_ON_DRIVE.SMS

Share this post:                                       
SCCM chats

http://technet.microsoft.com/en-in/cc678050(en-us).aspx (SCCM 2007 IBCM & Native Mode)

http://technet.microsoft.com/en-in/cc678049(en-us).aspx (SCCM 2007 Desired Configuration Management )

http://technet.microsoft.com/en-in/cc678048(en-us).aspx (Software Updates Management with System Center Configuration Manager 2007 )

http://technet.microsoft.com/en-in/cc678047(en-us).aspx (Operating System Deployment with System Center Configuration Manager 2007 )

 http://technet.microsoft.com/en-in/cc677236(en-us).aspx ((Deploying System Center Configuration Manager 2007 )

Share this post:                                       
New Virtual LABS for SCCM 2007

New Virtual LABS for SCCM 2007 http://technet.microsoft.com/en-us/virtuallabs/bb539977.aspx

  • TechNet Virtual Lab: Configuring Configuration Manager 2007 Security including PKI TechNet
  • TechNet Virtual Lab: Deploying System Center Configuration Manager (SCCM) 2007
  • TechNet Virtual Lab: Implementing Branch Distribution Points in System Center Configuration Manager (SCCM) 2007
  • TechNet Virtual Lab: Implementing Desired Configuration Management in System Center Configuration Manager (SCCM) 2007
  • TechNet Virtual Lab: Implementing Maintenance Windows for Software Distribution in System Center Configuration Manager (SCCM) 2007
  • TechNet Virtual Lab: Introduction to System Center Configuration Manager (SCCM) 2007
  • TechNet Virtual Lab: Managing Custom Application Updates using Systems Center Configuration Manager (SCCM) 2007
  • TechNet Virtual Lab: Managing Microsoft Updates with System Center Configuration Manager (SCCM) 2007
  • TechNet Virtual Lab: Upgrading SMS 2003 SP2 to System Center Configuration Manager (SCCM) 2007
  • TechNet Virtual Lab: Upgrading System Center Configuration Manager 2007 to Service Pack 1
  • Share this post:                                       
    Windows 7 beta 1 version available

    Microsoft’s Steve Ballmer announced the availability of a beta version 1 of Windows 7.
    Share this post:                                       
    Error sending DAV request. HTTP code 401, status 'Unauthorized'

    Some of the systems were not scan for ITMU, when I have checked the subnets for these systems, I have clicked that It has been assosciated with the new distribution point. I went through DataTransferService.log, for 2 to 3 systems and I got a way towards accomplishment. The log was totally full of errors(As shown below). 

     I went to distribution point server, navigate to SMS_DP_SMS PKGD$ in the IIS and browse it. Though browsing was enable, but still it wasn't. When I have gone through security events on DP server, there were lot of failed logons from the systems which were not able to scan for ITMU. That's it! I have done following steps and it solved my problem.

    1) Navigate to SMS_DP_SMSPKGD$ in IIS.

    2) Right click, go to properties

    3) Open a directory security tab and Edit the " Authentication and access control" 

    4) It will open below window. I have just check " Integrated Windows authentication" and click ok. 

    Share this post:                                       
    While distributing a first pkg to a new DP ...How DistMgr.log will look like? and how will be the process of copying?
    While distributing a first pkg to a new DP ...How DistMgr.log will look like? And how will be the process of copying?I have split the log so that it should be understandable.Everyone must be knowing SMSPKG<Driver letter>$ folder will not create until and unless you have not distributed any pkg to your New DP.

    Following are the log file contains. Here some terms used as follows...

    <New_DP_Server> ---- Server recently added as a DP.

    <Site_Code>-------------- SMS site Code

    <PKGID>------------------ Pkg which you have distributed to <New_DP_Server>

    <Custom_Port>-------- On this Cutom port SMS is working (If your SMS site is working on Cutom port then it will show this entry)


    Checking the DP folder path

    Start updating the package on server ["Display=\\<New_DP_Server>\"]MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\...

    Attempting to add or update a package on a distribution point.

    Established connection to ["Display=\\<New_DP_Server>\"]MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\

    The distribution point ["Display=\\<New_DP_Server>\"]MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\ doesn't point to an existing path.

    Checking the best drive from the available one

    Enumerating disks to find best candidate.

    IsPathSMSEligible() MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\C$\

    IsPathSMSEligible() MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\D$\

    The best drive for installing package on the distribution point ["Display=\\<New_DP_Server>\"]MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\ is D:\

    Share SMSPKGD$ does not exist on distribution point ["Display=\\<New_DP_Server>\"]MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\

    Creating SMSPKG<Drive Letter> folder

    Try to create export SMSPKGD$ on ["Display=\\<New_DP_Server>\"]MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\

    The drive share is accessible.

    Successfully created the directory for the export.

    Successfully inserted SMSPKGD$ as an export to ["Display=\\<New_DP_Server>\"]MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\

    Creating Sub directory under SMSPKG<Drive Letter> folder

    Attempting to create subdirectory <PKGID> under the export.

    The export is accessible.

    Successsfully created the package directory <PKGID>\ under the export.

    Successfully created sub directory <PKGID> off MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\SMSPKGD$\

    Setting up IIS

    IISPortsList in the SCF is "<Custom_Port>".

    Port = :80:

    Adding Port = :80:

    Adding Port = :<Custom_Port>:

    Successfully updated the port list in IIS.

    Successfully started the default website.

    Installed ISAPI on <New_DP_Server>, copied E:\SMS\bin\i386\smsfileisapi.dll to \\<New_DP_Server>\ADMIN$\system32\inetsrv\smsfileisapi.dll

    Successfully created application pool IIS://<New_DP_Server>/W3svc/AppPools/SMS Distribution Points Pool.

    Successfully created the virtual directory SMS_DP_SMSPKGD$ for the physical path D:\SMSPKGD$.

    Successfully added file extension C:\WINDOWS\system32\inetsrv\smsfileisapi.dll.

    Successfully added application dependency SMS Distribution Point.

    Checking free space and copying the pkg files

    Get access to the package directory and the number of free bytes at that location.

    Attempting to make an accessible connection to MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\SMSPKGD$\<PKGID>\, get its NOS path, and get its number of free bytes.

    Start updating the package on server ["Display=\\<New_DP_Server>\"]MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\...

    Attempting to add or update a package on a distribution point.

    No action specified for the package on server ["Display=\\<Central_Site_Server>\"]MSWNET:["SMS_SITE=<Site_Code>"]\\<Central_Site_Server>\.

    Established connection to MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\SMSPKGD$\<PKGID>\

    Getting the NAL path's NOS equivalent.

    The NOS path is \\<New_DP_Server>\SMSPKGD$\<PKGID>\

    Getting the number of free bytes.

    Established connection to ["Display=\\<New_DP_Server>\"]MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\

    Enumerating disks to find best candidate.

    The number of free bytes 31683208

    Successfully made an accessible connection, got a NOS path, and, if requested, got the number of free bytes at this location.

    IsPathSMSEligible() MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\C$\

    Successfully set access security on MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\SMSPKGD$\<PKGID>\ for package <PKGID>

    Copying <Central Site Sever Source path>\Test.vbs to \\<New_DP_Server>\SMSPKGD$\<PKGID>\Test.vbs, OK

    Successfully copied package <PKGID> from <Central Site Sever Source path> to MSWNET:["SMS_SITE=<Site_Code>"]\\<New_DP_Server>\SMSPKGD$\<PKGID>\

    Successfully created/updated the package server in the data source

    Performing cleanup prior to returning.

    Updating package info for package <PKGID>

    Only retrying local DP update for package <PKGID>, no need to replicate package definition to child sites or DP info to parent site.

    StoredPkgVersion (6) of package <PKGID>. StoredPkgVersion in database is 6.

    Share this post:                                       
    Sample Configurations and Common Performance Related Questions of SCCM 2007

    This document is designed to provide an overview of sample hardware configurations used in stress and scale testing for different size environments. Additionally, it answers common questions about planning and configuring for optimal performance in Configuration Manager 2007.

    http://download.microsoft.com/download/4/b/9/4b97e9b7-7056-41ae-8fc8-dd87bc477b54/Sample%20Configurations%20and%20Common%20Performance%20Related%20Questions.pdf

    Share this post:                                       
    Hash Mismatch

    What you gonna a do if you are getting following error in execmgr.log

    OnContentAvailable program ProgramName NOT available, 0x80091007 Fatal error 0x80008602 encountered for program ProgramName. This program will not retry.

     

    The problem because of hash mismatch. I referred KB artical http://support.microsoft.com/kb/907979 but upating Distribution point didnt solved my problem.But yes the 2nd method listed below from KB artical solved my problem.

     

    1. Use an account that has administrative credentials to log on to a computer that is acting as the SMS distribution point.
    2. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
    3. Expand the name of the server that is running IIS, expand Web Sites, expand Default Web Site, right-click SMS_DP_SMSPKGC$, and then click Properties.
    4. On the Virtual Directory tab, make sure that the Directory Browsing option is turned on, and then click OK.
    5. Repeat step 4 for each package subfolder in the SMS_DP_SMSPKGC$ virtual directory.

     

     

    Share this post:                                       
    warning message in SMS_Status_Manager Component with Message ID 1215

    what if you are getting following warning message in SMS_Status_Manager Component with Message ID 1215?

     

     

    SMS Status Manager received a status message reported by component "Advanced Client" running on computer "<server name >", and the time stamp on the message is more recent than the current system time on the site server. Possible cause: The system clock on computer "<server name>" is 32192 or more seconds ahead of the site server's system clock.Solution: Synchronize the system clock of computer "<server name>" with the site server's system clock. Please refer to your Windows NT Server documentation or the Microsoft Knowledge Base for further information. SMS Status Manager will process status messages with improper time stamps when the site server's system clock surpasses the improper time stamps. For example, this status message will not be processed for 32192 seconds. SMS Status Manager will continue to report this problem every 24 hours until you fix it. SMS Status Manager will not report this problem if the system clock of computer "<server name >" is less than 300 seconds ahead of the site server's system clock. This interval is configurable in the SMS site control file. Please refer to the Microsoft Knowledge Base for further information.

    Please follow the steps below

    1) Go to status filter rule.

    2) Create the rule as given below in the figures below

                                

    Note:- This behavior only occurs when the computer is using this particular runtime library when the transition date (the day we change to Daylight Saving Time) falls on the first day of the month. For more details please go through  http://support.microsoft.com/kb/295450

    Share this post:                                       
    SMS Client on X64 bit systems

    In my environment some X64 bit servers were not scanning for ITMU. When I was tried to troubleshooting the servers, I was not able to lookup CCM folder in system32 and System Management Icon in control panel but I was able to see SMS agent host service.

    After some digging I got to know following things

    Where you will find the system management icon?

    1)     Go to control panel. Click on view x86 control panel Icons

     

    2)      It will open in new window and there you will find System management  Icon

     

     

     

     

    Where you will find CCM folder in x64 bit computer?

     1)      You will find C:\WINDOWS\sysWOW64. In the same folder you will find VPcache folder.

     

     

     

     

    Share this post:                                       
    http verification .sms_aut (<Port number>) failed with status code 503, service unavailable

    If MPControl.log file throwing error “http verification .sms_aut (<Port number>) failed with status code 503, service unavailable” then check for your IIS application pool. SMS management point pool and CCM server framework pool might have stopped.

       For resolution please check site server’s for Netlogon service is stopped or not.

    Note: - After installing June 08 patches Netlogon service was stopped on some of the SMS secondary site which causes proxy management point stops working. Starting of Netlogon service solved our problem.

     

    Share this post:                                       
    Workgroup Clients in SMS 2003 (Trusted Root key)
    Management points need to authenticate to the clients to prevent attackers from inserting unauthorized management points and redirecting clients to them. When a management point is created, it creates a certificate to be used for signing. The certificate is self-signed and is valid for 99 years. It is created and stored in the certificate store on the management point.When the Advanced Client receives a message from the management point, the client uses one of two ways to verify that the message came from a valid management point. The message can be verified using Active Directory or the trusted root key.If the AD schema has not been extended and SMS does not have permissions to publish to Active Directory, the Advanced Clients switch to an alternate method to verify the authenticity of the management point and its certificate. Each primary site server generates a trusted root key. If the primary site is joined to a parent site, it eliminates its own trusted root key and instead trusts the trusted root key of the parent site. The function of the trusted root key is similar to a root certificate in a public key infrastructure. By signing the management point certificates with the private key of the trusted root key pair, and by making a copy of the public key of the trusted root key pair available to the Advanced Clients, clients can differentiate between valid management points and unauthorized management points. Advanced Clients require only the trusted root key if the Active Directory schema is not extended for SMS. The trusted root key is stored in WMI in the root\ccm\locationservices directory.

    If the Advanced Client has the wrong trusted root key then it will throw following errors in CertificateMaintaince.log and locationservices.log

    In my environment many of workgroup clients was giving above errors and so they are not reporting H/W inventory (Reporting to MP through Proxy management point)I tried to Manually Transferring Site Keys but I didn’t get any success and "removing of Key information" by running CCMSetup with the RESETKEYINFORMATION switch on many numbers of clients was not possible for me. Reinstalling of secondary site and reinstalling proxy management point solved my problem. And the clean log looks like this

    The reason why problem has been resolved? (When a new management point is created, its self-signed certificate is saved to a location in the registry. Site component manager collects the certificate from the registry and sends its certificate to its site server. If its site server is not the central site, the certificate is passed up through the hierarchy until it arrives at the central site where the trusted root key is kept. The central site server signs the management point’s certificate with the trusted root key and sends it back down through the hierarchy to the management point, along with a copy of the trusted root key. When the management point receives the copy of the trusted root key, it signs the trusted root key with its own private key.)

    For Better understanding please go through SMS Certificate Infrastructure

    Share this post:                                       
    OSD PXE Initiated troubleshooting 3

    Scenario:- ServerA :- Installed with AD and DNS 
                      Server B:- Installed with SCCM,DHCP,WDS with PXE Service point

    1) You have configured WDS

     You have created

    2) Boot image with drivers added and copied pkg to PXE DP and default DP

    3) Operating system image and copied pkg to PXE DP and default DP

    4) Task sequence & advertisement

    5) Added bare metal machines mac address to the advertise collection

    What do you do if Image boot with boot image and after the PE background appears it'd hang for a few minutes then restart.?

    Solution:- 

    You should check Enable command support (For testing only)" on Windows PE tab on your Boot image properties.

    1) Turned on a command shell in PE by pressing F8 .(Thanks to introductory Blogacast on OSD by Brain(Brian))

    2) Go to location x:\windows\temp\smsts. Open SMSts.log.

    3) If you found error
    "failed to download pxe variable file" as the first error followed by "pxegetpxedata failed"  also if you run ipconfig on command prompt, sometimes its shows 169 range ip and sometimes its shows correct one. 

    4) Enable  PortFast on your CISCO switches. By Enabling PortFast on you will able to deploy OS through PXE.(It works for me)

    Share this post:                                       
    OSD PXE Initiated troubleshooting 2

    Scenario:- ServerA :- Installed with AD and DNS 
                      Server B:- Installed with SCCM,DHCP,WDS
    with PXE Service point

    1) You have configured WDS,

    You have created

    2) Boot image with drivers added.

    3) Operating system image and copied pkg to PXE DP and default DP

    What do you do if you are getting following error in SMSPXE.log  ?

    Unable to delete directory C:\WINDOWS\TEMP\PXEBootFiles\Windows\Boot\PXE (0x80070005).  Continuing.

    Unable to delete directory C:\WINDOWS\TEMP\PXEBootFiles\Windows\Boot (0x80070005).  Continuing.

    Unable to delete directory C:\WINDOWS\TEMP\PXEBootFiles\Windows (0x80070091).  Continuing.

     
    Solution:- 

    1) Stopped WDS service.

    2) Go to location mention in the error , take a owner ship of folders and delete the folders

    3) Start WDS service. Check SMSPXE.log & you will find error will be disappear.
     

     

    Share this post:                                       
    OSD PXE Initiated troubleshooting 1

    Scenario:- ServerA :- Installed with AD and DNS 
                      Server B:- Installed with SCCM,DHCP,WDS
    with PXE Service point

    You have created

    1) Boot image with drivers added.

    2) Operating system image

    3) Task sequence & advertisement

    4) Added bare metal machines mac address to the advertise collection and...

    What do you do if bare metal image is giving TFTP time out while booting ?

    Solution:-

    MS doc says that if you have install WDS and DHCP on the same server then follow the process which is given in the link  http://technet.microsoft.com/en-us/library/bb680753.aspx

    I have tried the process given in the link (WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes) but this didn't work for me its giving me error, "WDS is not configured".

    I have configured WDS pl.on the following tab's and TFTP time out error gone at the booting .Check following pic.

     

     

     

     

    Share this post:                                       
    Download an updated version of the documentation for SCCM 2007

    Download an updated version of the documentation for Microsoft System Center Configuration Manager 2007 for a computer running the Configuration Manager console

    http://www.microsoft.com/downloads/details.aspx?FamilyID=81997356-7f18-48b2-a53a-d6f995a47f35&DisplayLang=en 

    Share this post:                                       
    Software updates in configuration manager(Remote WSUS server) -1

    Server1:- SCCM

    Server2 :- WSUS 

    1) Install SCCM on Server1.

    2) Add software update point role on Server1

     

    3) Install WSUS on Server2.

    4) Right click "site systems" on sccm console,add new server and select Server2

     

    5) Make sure SCCM and WSUS ports are same.

    6) Right click "update Repository" and click on "Run Synchronization". Active software point will start communicating with Microsoft update.After completing Synchronization with Microsoft update, It will start synchronizing with SCCM database. Please see log pics below

     

    Share this post:                                       
    Microsoft SMS 2003 SP3 Asset Intelligence Catalog Update

    Asset Intelligence enhances the inventory capabilities of SMS 2003 SP3 by extending hardware and software inventory. Many inventory classes improve the breadth of information gathered about hardware and software assets.

     http://www.microsoft.com/downloads/details.aspx?FamilyId=3653E00B-6A0F-4226-87D7-02D3DF2147D7&displaylang=en

     

    Share this post:                                       
    How to Disable the 8.3 Name Creation on NTFS Partitions, when it gives error in "SCCM prerequisite check result pane"

    While running a SCCM prerequisite check it's giving following error.

     

    I have gone through steps given in  http://support.microsoft.com/kb/121007/en-us to solved above problem.

    Share this post:                                       
    More Posts Next page »