Archive for August, 2013
During VMware vCenter 5.1 SSO install I got this error “Database connection has failed”.
Start “Microsoft SQL Server 2008 R2 > Configuration tools > SQL Configuration Manager” and should configure to set TCP Port property to 1433
Compacting the VHD by using the Hyper-V Manager did not work for me,
I found out that the procedure down will compact the VHD.
Shut down the Virtual Machine.
Start a command prompt,
run this comands in the following order :
- select vdisk file = c:\Hyper-V\VHD\Windows_7\D-drive.vhdx
- attach vdisk readonly
- compact vdisk
- detach vdisk
By default on Windows Server the Internet Explorer 9 Security setting Do not save encrypted pages to disk is enabled,
this setting prevents the VMware vSphere webclient from loading.
To correct this, disable this “feature” in IE9
- In Internet Explorer 9, from the Tools menu, select Internet options.
- Click the Advanced tab.
- Under Security, find the option Do not save encrypted pages to disk, uncheck the box.
After moving the Exchange databases, Exchange 2010 shows ContentIndexState at Crawling. (issues with the Content index catalog files).
Run the powershell command :
Get-MailboxDatabaseCopyStatus -Server WMLMBX01 | fl Name,*Index*
Name : Db03\MBX1
ContentIndexState : Crawling
Log in to MBX1
restart the MSExchange Search Indexer service on server MBX1
Open Exchange Management Shell :
Update-MailboxDatabaseCopy -Identity DB03\MBX1 -CatalogOnly
This will solve the issue.
Windows Management Instrumentation (WMI) filters allow you to dynamically determine the scope of Group Policy objects (GPOs) based on attributes of the target computer.
When a GPO that is linked to a WMI filter is applied on the target computer, the filter is evaluated on the target computer. If the WMI filter evaluates to false, the GPO is not applied (except if the client computer is running Windows 2000, in which case the filter is ignored and the GPO is always applied). If the WMI filter evaluates to true, the GPO is applied.
WMI makes data about a target computer available for administrative use. Such data can include hardware and software inventory, settings, and configuration information. For example, WMI exposes hardware configuration data such as CPU, memory, disk space, and manufacturer, as well as software configuration data from the registry, drivers, file system, Active Directory, the Windows Installer service, networking configuration, and application data.
A WMI filter consists of one or more queries based on this data. If all queries are true, the GPO linked to the filter will be applied. The queries are written using the WMI Query Language (WQL), a SQL-like language. Queries can be combined with AND and OR logical operators to achieve whatever effect the administrator wants. Each query is executed against a particular WMI namespace. When you create a query, you must specify the namespace. The default is root\CIMv2, which is appropriate for most WMI queries.
The WMI filter is a separate object from the GPO in the directory. To apply a WMI filter to a GPO, you link the filter to the GPO. This is shown in the WMI filtering section on the Scope tab of a GPO. Each GPO can have only one WMI filter, however the same WMI filter can be linked to multiple GPOs.
WMI filters, like GPOs, are stored on a per-domain basis. A WMI filter and the GPO it is linked to must be in the same domain.
To create a WMI filter for Windows 7 computers :
- Open Group Policy Management
- Expand the tree until you find “Group Policy Objects“
- Right Click “WMI Filters” and select “New“
- On the “New WMI Filter” name the filter and click “Add.”
- On the “WMI Query” window, leave the namespace and copy the query below and click “OK“
select * from Win32_OperatingSystem where Version like “6.1%” and ProductType=”1″
6. Click “Save” on the “New WMI Filter” window.
select * from Win32_OperatingSystem where Version like “x.x%”
This part queries the OS version.
The x.x% number must be changed for the different OS versions.
“6.2%” = Windows 8 or Windows Server 2012
“6.1%” = Windows 7 or Windows Server 2008 R2
“6.0%” = Windows Vista or Windows Server 2008
“5.2%” = Windows XP
“5.0%” = Windows 2000
This part queries the role of the computer.
“1” = Client
“2” = Domain controllers
“3” = Member server or server that are not a Domain Controller
The following table shows sample code for several WMI filters.
select * from Win32_OperatingSystem WHERE Version LIKE “5.1%”
select * from Win32_OperatingSystem WHERE Version LIKE “6.1%” and ProductType = “1”
select * from Win32_OperatingSystem WHERE Version LIKE “6.2%” and ProductType = “1”
Windows Server 2003 R2
select * from Win32_OperatingSystem WHERE Version LIKE “5.2%”
Windows Server 2008
select * from Win32_OperatingSystem WHERE Version LIKE “6.0%” AND ( ProductType = “2” or ProductType = “3” )
Windows Server 2008 R2
select * from Win32_OperatingSystem WHERE Version LIKE “6.1%” AND ( ProductType = “2” or ProductType = “3” )
Windows Server 2012
select * from Win32_OperatingSystem WHERE Version LIKE “6.2%” AND ( ProductType = “2” or ProductType = “3” )
|Criterion||Administrator’s intent||WMI filter|
|Configuration||Avoid turning on netmon on computers that can have multicasting turned on.||Select * from Win32_NetworkProtocol where SupportsMulticasting = true|
|Time zone||Apply policy on all servers located on the East Coast of the United States.||Root\cimv2 ; Select * from win32_timezone where bias =-300|
|Hotfix||Apply a policy on computers that have a specific hotfix.||Root\cimv2 ; Select * from Win32_QuickFixEngineering where HotFixID = ‘q147222′|
|Software inventory||Assign software only on computers already having either of two software packages.||Root\cimv2;Select * from Win32_Product where name = “MSIPackage1″ OR name = “MSIPackage2″|
|Operating system||Only target computers running Windows XP Professional.||Root\CimV2; Select * from Win32_OperatingSystem where Caption = “Microsoft Windows XP Professional”|
|Resources||Target only machines that have at least 600 megabytes (MB) available.||Root\CimV2; Select * from Win32_LogicalDisk where FreeSpace > 629145600 AND Description <> “Network Connection”|
|Make or model||Target Toshiba Tecra models 800 and 810.||Root\CimV2; Select * from Win32_ComputerSystem where manufacturer = “Toshiba” and Model = “Tecra 800″ OR Model = “Tecra 810″|