Monday, July 28, 2014

.Net Framework 3.5 Features on Windows Server 2012

.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.

We can choose one of the following installation methods:

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.


2. Using PowerShell, specify the source files path when installing. 

Install-WindowsFeature NET-Framework-Core –Source D:\Sources\sxs

3. Using DISM from the command prompt, specify the source files path parameter:
DISM /Online /Enable-Feature /FeatureName:NetFx3 /Source:d:\sources\sxs

4. Using a file share containing the sxs folder, specify the unc share path:
Install-WindowsFeature NET-Framework-Core –Source \\ServerName\ShareName\sxs


Thursday, May 10, 2012

Management Point Rejected policy request

  • Check the Client GUID (e.g, GUID:D06707E1-69E6-485D-B3F3-6678511C53A2).
Run The Query Log on to SQL Server Management Studio and run this query against SCCM database
select * from dbo.system_data where smsid0 = 'GUID here'
  • It will give you the PC name, then locate PC in SCCM collections, uninstall SCCM client then reinstall the client.

Query to Find Collections With Maintenance Windows

 Run this query against the SCCM site database using SQL Server Management Studio.

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

Thursday, March 29, 2012

Heart Beat is beating my heart

I 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.
Is the client installed?
Client type (Legacy, Advanced, or Device)
Client version
NetBIOS Name
Character encoding used by the client
Default system locale identifier (typically representative of the client’s language)
Date and time of the DDR
Date and time of last DDR
Short name of system
Currently logged in (interactive) user
FQDN of system
IP Network ID
Platform ID (this is an encoding of the OS version)
AD Site Name
IP Address(es)
MAC Address(es)
Domain name
Assigned (Primary) Site
Hardware ID
Identifying number (computer system)
Product name (computer system)
UUID (of the computer system)
Version (computer system)
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.
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 Clear Install Flag and Delete Aged Discovery Data maintenance tasks perform their jobs. Note that the Delete Inactive Client Discovery Data does not directly use the heartbeat time. Instead, Client Status Reporting (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.
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.
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.
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.
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.
Heartbeat Discovery is the discovery process that submits a client's installation status to its assigned site.
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.

Sunday, October 2, 2011

Creating Custom Reports by Tool

The 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.

Here is the link to download the tool:

Wednesday, September 28, 2011

MMC stops working when running queries in large environment

Few 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.

Go to the adminUI.log and find the ErrorCode = 2152205056

if this is the error then fillow the below steps -

1. Run WBEMTest and connect to Root.

2. Click 'Open Instance', enter __ProviderHostQuotaConfiguration=@ and click OK.

3. Locate the MemoryPerHost property and double click it to bring up the editor.

4. Change the value to 536870912 and click Save Property. [Note: 536870912 is 512MB written in Bytes.
5. Locate the HandlesPerHost property, note the current value, set it to 8192 and click Save Property.

6. Click Save Object, exit WBEMTest and reboot the site server and test again.

Note : Make sure that you have saved the curren value some where.

Sunday, September 25, 2011

WSUS Maintenance: failed synchronization

You may have received error from wsyncmgr.log stating " 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"
You can Resolve the issue in following ways
- ReIndex the WSUS 3.0atabase
-Run WSUS Cleanup wizard
Run the WSUS Server Clean-up Wizard from the bottom of the WSUS hierarchy to the top and NEVER from the top down.
Run the WSUS Server Clean-Up Wizard throughout the hierarchy on a monthly basis.
-Open WSUS administration console, select Options, and then Server Cleanup Wizard
-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.
- It will begin the cleanup process, and will present a summary of its work when it is finished. Click Finish to complete the process