tag:blogger.com,1999:blog-15012516393715055352024-03-05T23:52:51.624-08:00Manish Pathak|SCCM Specialist|Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.comBlogger21125tag:blogger.com,1999:blog-1501251639371505535.post-56097325681121454752014-07-28T14:39:00.003-07:002014-07-28T14:45:21.369-07:00.Net Framework 3.5 Features on Windows Server 2012<div dir="ltr" style="text-align: left;" trbidi="on">
<span style="font-family: Verdana, sans-serif; font-size: x-small;">.Net Framework 3.5 is not a default feature of Windows 2012, therefore we need to install this feature using SxS( side by side) located on your DVD media of Windows 2012 server.</span><br />
<span style="font-family: Verdana, sans-serif; font-size: x-small;"><br /></span>
<span style="font-family: Verdana, sans-serif; font-size: x-small;">We can choose one of the following installation methods:</span><br />
<span style="font-family: Verdana, sans-serif; font-size: x-small;"><br /></span>
<span style="font-family: Verdana, sans-serif; font-size: x-small;">1. Using the Add Roles and Features Wizard, specify an alternate source path using the link at the bottom of the wizard. For example, D: is my Windows Server DVD media.</span><br />
<span style="font-family: Verdana, sans-serif; font-size: x-small;"><br /></span>
<span style="font-family: Verdana, sans-serif; font-size: x-small;">D:\Sources\sxs</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif; font-size: x-small;">2. Using PowerShell, specify the source files path when installing. </span><br />
<br />
<span style="font-family: Verdana, sans-serif; font-size: x-small;">Install-WindowsFeature NET-Framework-Core –Source D:\Sources\sxs</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif; font-size: x-small;">3. Using DISM from the command prompt, specify the source files path parameter:</span><br />
<span style="font-family: Verdana, sans-serif; font-size: x-small;">DISM /Online /Enable-Feature /FeatureName:NetFx3 /Source:d:\sources\sxs</span><br />
<span style="font-family: Verdana, sans-serif; font-size: x-small;"><br /></span>
<span style="font-family: Verdana, sans-serif; font-size: x-small;">4. Using a file share containing the sxs folder, specify the unc share path:</span><br />
<span style="font-family: Verdana, sans-serif; font-size: x-small;">Install-WindowsFeature NET-Framework-Core –Source \\ServerName\ShareName\sxs</span><br />
<div>
<br /></div>
<div>
<br /></div>
<div style="background-color: white; font-family: 'Trebuchet MS', Tahoma, sans-serif; font-size: 12px;">
</div>
</div>
Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-30844415586576691002012-05-10T13:29:00.002-07:002012-05-10T13:29:24.355-07:00Management Point Rejected policy request<div dir="ltr" style="text-align: left;" trbidi="on">
<ul><br /><br />
<li>Check the Client GUID (e.g, GUID:D06707E1-69E6-485D-B3F3-6678511C53A2).</li>
</ul>
Run The Query Log on to SQL Server Management Studio and run this query against SCCM database<br />
select * from dbo.system_data where smsid0 = 'GUID here'<br />
<ul>
<li>It will give you the PC name, then locate PC in SCCM collections, uninstall SCCM client then reinstall the client.<br />
<br />
</li>
</ul>
</div>Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-29209834056333990342012-05-10T13:01:00.004-07:002012-05-10T13:01:54.470-07:00Query to Find Collections With Maintenance Windows<div dir="ltr" style="text-align: left;" trbidi="on">
Run this query against the SCCM site database using SQL Server Management Studio.<br />
<br />
SELECT c.Name, c.Comment,SW.Description, SW.StartTime, SW.Duration FROM v_ServiceWindow SW JOIN v_Collection C ON C.CollectionID = SW.CollectionID ORDER BY c.Name<br />
<br />
<br />
</div>Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-65233901129523702722012-03-29T07:54:00.003-07:002012-03-29T15:21:26.288-07:00Heart Beat is beating my heartI have been often come across discussion where my friends differs about the macro idea about Heatbeat discovery resulting into beating my heart. So here is crux of what exact a heartbeat is. Below are the information contained as part of Heartbeat Discovery.<br />Is the client installed?<br />Client type (Legacy, Advanced, or Device)<br />Client version<br />NetBIOS Name<br />Character encoding used by the client<br />Default system locale identifier (typically representative of the client’s language)<br />Date and time of the DDR<br />Date and time of last DDR<br />Short name of system<br />Currently logged in (interactive) user<br />FQDN of system<br />IP Network ID<br />Platform ID (this is an encoding of the OS version)<br />AD Site Name<br />IP Address(es)<br />MAC Address(es)<br />Domain name<br />Assigned (Primary) Site<br />Hardware ID<br />Identifying number (computer system)<br />Product name (computer system)<br />UUID (of the computer system)<br />Version (computer system)<br />Heartbeat Discovery messages are quite small and have negligible overhead on the client. Cumulatively, a large number could impact an under-powered management point, however, so setting them too frequently is not advisable. Out of the box, the default is 7 days. I typically set this down to every 1 day and know others do it even more often. I would never recommend setting this to less than 1 or 2 hours except in very small environments – there isn’t really any value in doing so anyway as nothing in the above list normally changes that frequently.<br />The Heartbeat Discovery also serves as a “keep alive” or “yes I am alive” message from the client to the site server. Based on this, the <a href="http://technet.microsoft.com/en-us/library/bb694040.aspx">Clear Install Flag</a> and <a href="http://technet.microsoft.com/en-us/library/bb693856.aspx">Delete Aged Discovery Data</a> maintenance tasks perform their jobs. Note that the <a href="http://technet.microsoft.com/en-us/library/bb693646.aspx">Delete Inactive Client Discovery Data</a> does not directly use the heartbeat time. Instead, <a href="http://technet.microsoft.com/en-us/library/cc161956.aspx">Client Status Reporting</a> (available in R2 and R3), uses the last heartbeat time along with last hardware inventory, last software inventory, and last policy polling time to determine if a client is inactive. Once a client is marked inactive by Client Status Reporting, it is then subject to the Delete Inactive Client Discovery Data task.<br />This “keep alive” purpose of the heartbeat discovery should also influence your choice of how often to set the interval; i.e., you shouldn’t set so infrequently that it might get accidentally marked inactive or not installed by one of the above mentioned maintenance tasks.<br />Note that you can manually initiate a Heartbeat Discovery anytime on a client from the Configuration Manager Control Panel applet by navigating to the actions tab, selecting Discovery Data Collection Cycle, and then pushing the Initiate Action button.<br />Heartbeat Discovery forces the rediscovery of active clients that have been deleted from the Configuration Manager database by the administrator, or by a database maintenance task.<br />If you accidentally delete a computer from the Configuration Manager console, it will automatically "come back" if it is still active on the network. You can either wait for the next Heartbeat Discovery cycle to run, or you can hurry things along by selecting the Discovery Data Collection Cycle on the client Configuration Manager Properties: Actions tab, and click OK.<br />Heartbeat Discovery is the discovery process that submits a client's installation status to its assigned site.<br />The client might be installed but the client state in the Configuration Manager console continues to display No for its Client state if the site hasn't received the client's discovery data record (DDR) from Heartbeat Discovery. This will be the case if the client cannot communicate with its management point.Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-66088513870995567932011-10-02T18:46:00.000-07:002011-10-02T19:08:32.601-07:00Creating Custom Reports by ToolThe Windows Installer CreatingCustomReportsByUsingSQLViews.msi package provides information that will help you to create custom reports, determine which Configuration Manager SQL views contain the information you need for your reports, and identify a path between the necessary SQL views and determine what columns can be used to join them.<br /><br />Here is the link to download the tool:<br /><br /><a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=87BBE64E-5439-4FC8-BECC-DEB372A40F4A&displaylang=en">http://www.microsoft.com/downloads/details.aspx?FamilyId=87BBE64E-5439-4FC8-BECC-DEB372A40F4A&displaylang=en</a>.Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-65997898121063469152011-09-28T16:26:00.000-07:002011-09-28T16:38:47.869-07:00MMC stops working when running queries in large environmentFew months back my patching team comaplins that during patch cycle the MMC get hanged and become unresponsive. During patch cycle thousands of computers needs to be quried to put in a collection. This usually happens in large SCCM environment. Here is the resolution.<br /><br />Go to the adminUI.log and find the ErrorCode = 2152205056<br /><br />if this is the error then fillow the below steps -<br /><br />1. Run WBEMTest and connect to Root.<br /><br />2. Click 'Open Instance', enter __ProviderHostQuotaConfiguration=@ and click OK.<br /><br />3. Locate the MemoryPerHost property and double click it to bring up the editor.<br /><br />4. Change the value to 536870912 and click Save Property. [Note: 536870912 is 512MB written in Bytes.<br />5. Locate the HandlesPerHost property, note the current value, set it to 8192 and click Save Property.<br /><br />6. Click Save Object, exit WBEMTest and reboot the site server and test again.<br /><br />Note : Make sure that you have saved the curren value some where.Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-62720175164937090582011-09-25T15:21:00.000-07:002011-09-25T15:59:30.442-07:00WSUS Maintenance: failed synchronizationYou may have received error from <strong>wsyncmgr.log </strong>stating " <em>Sync failed: LocalDBOtherError: SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.~~at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction</em>"<br />You can Resolve the issue in following ways<br />- <strong>ReIndex the WSUS 3.0atabase</strong><br /><a href="http://gallery.technet.microsoft.com/ScriptCenter/en-us/6f8cde49-5c52-4abd-9820-f1d270ddea61">http://gallery.technet.microsoft.com/ScriptCenter/en-us/6f8cde49-5c52-4abd-9820-f1d270ddea61</a><br />-<strong>Run WSUS Cleanup wizard</strong><br />Run the WSUS Server Clean-up Wizard from the bottom of the WSUS hierarchy to the top and NEVER from the top down.<br />Run the WSUS Server Clean-Up Wizard throughout the hierarchy on a monthly basis.<br /><a href="http://gallery.technet.microsoft.com/ScriptCenter/en-us/fd39c7d4-05bb-4c2d-8a99-f92ca8d08218">http://gallery.technet.microsoft.com/ScriptCenter/en-us/fd39c7d4-05bb-4c2d-8a99-f92ca8d08218</a><br />------------------OR--------------------<br />-Open WSUS administration console, select Options, and then Server Cleanup Wizard<br />-This wizard will remove unneeded content and computers that have not contacted the server for 30 days(Default) or more. Select all possible options, and then click Next.<br />- It will begin the cleanup process, and will present a summary of its work when it is finished. Click Finish to complete the processManish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-5040492258224033352011-09-25T14:35:00.000-07:002011-09-25T15:07:17.981-07:00Checking SMS/SCCM site information publishing in Active DirectoryThis happens If Active Directory Schema is not extended and the computer holding SCCM server does not have full rights on Active directory container. This can be rectified in following way...<br />-open Active Directory Users and Computers.<br />-On the View menu, click Advanced Features.<br />The Active Directory Computers and Users window displays additional Active<br />Directory information, including displaying the System container. You will grant<br />rights to the System container to allow the Configuration Manager site server to<br />publish data to Active Directory.<br />-In the console tree, expand domain( name of your domain), and then click<br />System.<br />-On the Action menu, click Properties.<br />-Click the Security tab.<br />The System Properties dialog box displays the security permissions on the<br />System container. Notice that the Configuration Manager site server computer<br />(SMSServer) is not listed.<br />-Click Add.<br />The Select Users, Computers, or Groups dialog box appears.<br />-Click Object Types.<br />The Object Types dialog box appears.<br />-Under Object types, click Computers, and then click OK.<br />-In the Enter the object names to select field, type smsserver name and then click OK.<br />- The Select Users, Computers, or Groups dialog box appears. Notice that the<br />Configuration Manager site server computer is now listed with<br />Read rights.<br />-Under Permissions for SMSSERVER, click Full Control under Allow, and then<br />click Advanced.<br />The Advanced Security Settings for System dialog box appears displaying the<br />rights for various accounts.<br />-Under Name, click on SMS SERVER name, and then click Edit.<br />The Permission Entry for System dialog box appears displaying the rights for<br />SMSServer$.<br />-In the Apply onto field, click This object and all child objects, and then click<br />OK.<br />The Advanced Security Settings for System dialog box appears.<br />-Click OK.<br />The System Properties dialog box appears.<br />-Click OK.<br />The Active Directory Computers and Users window appears. You can leave this<br />window open if you want to view information that Configuration Manager<br />publishes to Active Directory after installation.<br />---------------------------<br />Logs to check<br /><strong>Hman.log</strong> for the following information<br /><br />" Active Directory DS Root:DC= Domainname here,DC=com<br />Searching for the System Management Container.<br />System Management container exists.<br />Site objects existing in AD: cn=SMS-Site-Site code here.<br />Searching for SMS-Site-<site> Site Object.<br />SMS-Site-<site> exists, updating.<br />SMS-Site-< Site Code here> successfully updated. "<br />---------<br /><br /><strong>sitecomp.log </strong>for the following information<br /><br />Publish Servers in Active Directory.<br />DS Root:DC=SCCMSERVER,DC=DOMAINNAME ,DC=com<br />Searching for the System Management Container.<br />LDAP://CN=System Management,CN=System,DC=SCCMSERVER,DC=DOMAINNAME,DC=com container exists.<br />Site System is the Default Management Point.<br />No Fallback Status Point installed on the Site<br />Size of Signing Certificate: 0<br />Signing Certificate:<br />Checking configuration information for server: SECONDARY.<br />SECONDARY is the Default MP.<br />Updated MP Configuration for SECONDARY.<br />Installing Security settings on site system ...<br />Security settings are up to date for SECONDARY.<br />Installing DNS publishing settings on site system ...<br />DNS publishing settings are up to date for SECONDARY.<br />Publishing SECONDARY(SECONDARYSERVER NAME.SCCMSERVER.DOMAINNAME.com) as a Management Point into Active Directory.<br />SMS-MP-SECONDARY SERVER SITE CODE -SECONDARY successfully updated.Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-28192541944363750852011-09-25T14:19:00.000-07:002011-09-25T14:25:50.566-07:00Query for client does not receive advertisementThis will list all clients that never get advertisement.<br /><br />Log on to SQL Server Management Studio and run this query against SCCM database<br /><br />select distinct count(v_ClientAdvertisementStatus.resourceid) as [Number of Adverts],sys.Active0,sys.Client0,sys.Client_Version0,sys.Netbios_Name0,<br />sys.Operating_System_Name_and0,sys.Obsolete0,<br />sys.Resource_Domain_OR_Workgr0,sys.User_Domain0,<br />sys.User_Name0 from v_R_System sys right join v_ClientAdvertisementStatus on sys.resourceid=v_ClientAdvertisementStatus.resourceid where sys.ResourceID not in (select distinct ResourceID from v_ClientAdvertisementStatus where v_ClientAdvertisementStatus.LastStateName = 'Succeeded') group by sys.Active0,sys.Client0,sys.Client_Version0,<br />sys.Netbios_Name0,sys.Operating_System_Name_and0,<br />sys.Obsolete0,sys.Resource_Domain_OR_Workgr0,<br />sys.User_Domain0,sys.User_Name0Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-86987937583468536942011-09-25T13:23:00.001-07:002011-09-25T14:16:31.150-07:00Management Point Rejected policy request: Broken Clients<ul><br /><li>Check MPStatus.log :Error will look like this "<span style="font-family:arial;"> <em>MP has rejected a policy request from GUID:A2062E3F-655F-4F4A-97C9-2E6D41B31D72 because it was not approved. The operating system reported error 2147942405: Access is denied"</em> </span></li><br /><li><strong>ClientIDManagerStartup.log</strong> indicate that the client has been registered? That's the first step. If not, no policies can be downloaded (client will automatically retry the registation process every 10 minutes You can see that happen in the ClientIDManagerStartup.log. There's nothing you have to do to attempt the re-registration process)</li><br /><li>Run a query to get the computer name using GUID</li></ul><br /><p></p><br /><p>Log on to SQL Server Management Studio and run this query against SCCM database<br />select * from dbo.system_data where smsid0 = 'GUID' </p><br /><ul><br /><li>This Query will return computer name. Find the PC locate then and uninstall. would be good if you use delcert comannd after uninstalling. </li><br /><li>Install the Client , take a look of MPstatus/ Clientidpstartup.log, I am sure you will receive a success message.<br /></li></ul>Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-48744482132037120862011-09-25T13:07:00.000-07:002011-09-25T13:22:47.854-07:00Management Point verification<ul><br /><li>Do a check on <strong>MPsetup.log</strong>. check the last line in the log "MP is install successfully. If you find any problem in MPSetup.log, then verify MPMSI.log for more information on the issue. </li><br /><li>Do a check on IIS , check if virtual directory named SMS_MP under default website is created.</li><br /><li>check MPcontarol.log for the status code "200"</li><br /><li>Check with following URL's</li></ul><br /><p>h<a href="http:///sms_mp/.sms_aut?mplist">ttp://<mp>/sms_mp/.sms_aut?mplist</a><br /><a href="http:///sms_mp/.sms_aut?mpcert">http://<mp>/sms_mp/.sms_aut?mpcert</a> </p><br /><p></p>Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-80775313797847849242010-08-10T06:55:00.000-07:002010-08-10T07:13:09.896-07:00Re assignment of SCCM client into different Hierarchywhen we reassign SCCM Client from one Hierarchy to another, the client already has a trusted root key from its original hierarchy. Reassigning the client to a new hierarchy means that the client will also be assigned to a new management point. When both the trusted root key and the management point changes, by default, the client will become unmanaged. In this scenario, the Advanced Client component will send the status message ID 10822 to the site, with a description that it encountered a certificate for a management point that it could not verify. Additionally, the client log file Locationservices.log will display the errors like : The trusted key, mp certificate and the mp machine have changed on server. The client cannot validate the authentication information.<br />--------<br />If you want to just reassign a client to a new hierarchy without reinstalling it, you have two options:<br /><br />•Pre-provision the client with the trusted root key for the new hierarchy, using one of the procedures in the topic <a href="http://technet.microsoft.com/en-us/library/bb680504.aspx">How to Pre-Provision the Trusted Root Key on Clients</a>. This is the recommend method because it is more secure.<br />•Remove the trusted root key from client, using the procedure in the topic How to Remove the Trusted Root Key.<br /><br />Alternatively, when you reassign the client, you can also reinstall it by using a method that includes the trusted root key. For example:<br /><br />•Client push, which automatically includes the trusted root key without your having to specify it.<br />•CCMSetup and include the option SMSPublicRootKey or SMSROOTKEYPATH.Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-90142778023036825742010-08-03T08:44:00.000-07:002010-08-03T08:45:44.386-07:00Force DCM Evaluation RemotelyOn Error Resume Next<br />CompName = Wscript.Arguments(0)<br />If compname = "" Then<br /> CompName = InputBox("Input a Computer name or IP", "Computer Name",CompName)<br />End If<br />err.clear<br />set DCMInvoke = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &_<br />CompName & "\root\ccm\dcm:SMS_DesiredConfiguration")<br />if err.number <> 0 then<br />msgbox "unable to access " & CompName & vbcr &_<br /> "Error: " & err.description,,"SMS DCM Trigger Evaluation"<br />else<br /> Set objSWbemServices = GetObject("winmgmts:\\" & CompName & "\root\ccm\dcm")<br /> Set colSWbemObjectSet = objSWbemServices.ExecQuery("SELECT * FROM SMS_DesiredConfiguration")<br /> For Each objSWbemObject In colSWbemObjectSet<br /> DCMInvoke.TriggerEvaluation objSWbemObject.Name,objSWbemObject.Version<br /> Next<br />end ifManish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-10198701481675591032010-08-02T08:19:00.000-07:002010-08-02T08:23:24.594-07:00Waiting to install package on some DP'sModify the PkgStatus table on the central site server SQL database and then refresh the affected DP's<br /><br /><br />update pkgstatus set Status = 2 where id = '<package ID>' and sitecode = '<site code>' and type = 1<br />update pkgstatus set SourceVersion = 0 where id = '<package ID>' and sitecode = '<site code>' and type = 1Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-20748367387688944662010-07-30T09:17:00.000-07:002010-07-30T09:20:01.765-07:00SCCM Client to Wait due to Conflicting RecordsIf you have an SCCM client that's installed correctly, but seems to not be performing any usual SCCM actions, check the the "ClientIDManagerStartup.log" log file (located under %WIN%\SYSTEM32\CCM\LOGS).<br /><br />Look for the following lines in the "ClientIDManagerStartup.log" log file:<br /><br />RegTask: Client is not registered. Sending registration request...<br />RegTask: Client registration is pending.<br />Client is pending registration. Sending confirmation request...<br />Server requested reset. Restarting client registration<br />Already refreshed within the last 10 minutes, Sleeping for the next 9 minutes before reattempt.<br /><br />This indicates the Hardware ID for the SCCM client has recently changed, and there are multiple records for the client in the SCCM database. The SCCM client will not perform any actions until the "conflicting records" issue is resolved.<br /><br />To resolve the issue, an SCCM administrator must open the SCCM console and merge the multiple records together into a single record. Once this is completed, the client will update its records and start performing normal tasks.Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com1tag:blogger.com,1999:blog-1501251639371505535.post-28763631300483001622010-07-30T09:12:00.000-07:002010-07-30T09:15:01.122-07:00Client Inventory is not showing in DATABASEI recently had a problem with client inventory data not being present in the SCCM database. I was making a query to find machines running Windows XP with Service Pack 3, and it only reported back 6 or 7 clients,Knowing that a lot more had the service pack installed.<br /><br />I checked the logs on some of my clients and they seemed to report both hardware and software inventory just fine, and sent it to my management point. I checked the logs on my SCCM server and every time i recieved the inventory report from clients I got an SQL error saying that the rows in my table could not be updated. This lead me to believe that the client had never been in the table, and as suspected, my OperatingSystem table (the table that contains data about a client operating system, and in this case what service pack is installed) only had a few machines present. Somehow my management point had stopped inserting data into the tables.<br /><br />I resolved this issue simply by removing and re-installing my management point role on my SCCM server, but it lead to several hours of head-scratching!Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-63750414337372682112010-07-30T05:44:00.000-07:002010-07-30T05:51:18.311-07:00WMI ReapirSteps to rebuild WMI manually<br />1. Assure your account has administrative privilege<br />2. Type the command in a command prompt window (or paste below commands on the window).<br /><br />net stop winmgmt /y<br /><br /><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh6K31WAbt007lmXd5jqXEs_CWlMNr6h4NwNILS8Ph5QNxsQoYBeepmQ55hX_AlkEATyYHiG5HPPrzzgrvF6Q5oZVT9sP-HCek1x_vErntbVsEklCkwh1l_dGh_TCB2xUDPudhLoAbew7Zk/s1600/7-30-2010+6-17-34+PM.jpg"><img style="TEXT-ALIGN: center; MARGIN: 0px auto 10px; WIDTH: 320px; DISPLAY: block; HEIGHT: 28px; CURSOR: hand" id="BLOGGER_PHOTO_ID_5499680278579547794" border="0" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh6K31WAbt007lmXd5jqXEs_CWlMNr6h4NwNILS8Ph5QNxsQoYBeepmQ55hX_AlkEATyYHiG5HPPrzzgrvF6Q5oZVT9sP-HCek1x_vErntbVsEklCkwh1l_dGh_TCB2xUDPudhLoAbew7Zk/s320/7-30-2010+6-17-34+PM.jpg" /></a><br /><br />c:<br />cd %windir%\system32\wbem<br />if exist %windir%\system32\wbem\repository.old rmdir /s /q repository.old<br />rename %windir%\system32\wbem\repository repository.old<br />for /f %i in ('dir /b *.dll') do regsvr32 /s %i<br />for /f %i in ('dir /b *.mof *.mfl') do mofcomp %iManish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-25576927099498796622010-07-22T13:35:00.000-07:002010-07-22T13:35:03.342-07:00Blogger Buzz: Blogger integrates with Amazon Associates<a href="http://buzz.blogger.com/2009/12/blogger-integrates-with-amazon.html">Blogger Buzz: Blogger integrates with Amazon Associates</a>Manish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-63229299978454410242010-07-19T05:36:00.000-07:002010-07-21T13:53:56.961-07:00Pending packages/Task Tequence troubleshootingTo resolve this issue is to modify the PkgStatus table on the central site server SQL database, and then refresh the affected distribution points.Run The SQL query for each affected distribution point.<br /><br />update pkgstatus set Status = 2 where id = '< package ID >' and sitecode = '< site code >' and type = 1<br /><br />update pkgstatus set SourceVersion = 0 where id = '< package ID >' and sitecode = '< site code >' and type = 1<br /><br />Note: <br />Microsoft stated that this issue can randomly occur in larger SCCM environments with large packages and slow WAN links, and they are unable to exactly pinpoint the problem due to its random natureManish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-17330875051774696232010-07-16T14:57:00.000-07:002010-07-18T13:38:30.104-07:00SCCM console get hanged in monthly patch cycle- Run WBEMTest and connect to Root<br /> - Click 'Open Instance', enter __ProviderHostQuotaConfiguration=@ and click OK<br /> - Locate the MemoryPerHost property and double click it to bring up the editor<br /> - Note the current value, replace it with 402653184 and click Save Property<br /> - Locate the HandlesPerHost property, note the current value, set it to 16384 and click Save Property<br /> - Click Save Object and then Exit WBEMTestManish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0tag:blogger.com,1999:blog-1501251639371505535.post-20098437127517236432008-09-18T16:25:00.000-07:002008-09-18T16:29:02.843-07:00My experiencesManish Pathakhttp://www.blogger.com/profile/04695438421572286300noreply@blogger.com0