WMI to TMG

Hey,
We've recently implemented VAMT 3.1 and this is working well, except for our TMG servers. The VAMT error message is 'Unable to connect to the WMI service on the remote computer'.
Presumably TMG is set to block this to itself out of the box, so I went through the process of disabling strict RPC compliance in the system policy and creating a rule allowing WMI to Local Host, but it still doesn't work.
Is there any guidance in setting up WMI from VAMT to TMG? One of our TMG servers is in a remote site (TMG to TMG site to site VPN), so i'll need access to that one too.
Thanks.

Sorry, can you clarify steps 3 and 4 please.
3. Firewall polkicy rule with custom protocol port 10002 TCP, Direction outbound <---- From where
and To where?
4: in the System Policy rules search for the rule with protocol RPC(all interfaces)
properties -From“ edit group „Enterprise Remote Management Computers“
exclude VAMT computer from the INTERNAL network definition (split Internal address range to exclude VAMT
computer).
Do what with Enterprise Remote Management Computers? Add it/delete it? And then am I adding or deleting
INTERNAL from this policy's From tab?
And do I really need to exlude VAMT machine from INTERNAL network? That's just so silly!

Similar Messages

How to populate values in F4 help based on another F4 help in a TMG

Hello All,
I have created a TMG for a table. Have added that to customization also. Now, in that table I have 2 fields say carrid and connid. In the F4 help of carrid, all carrids will be displayed. Now if the user selects one carrid, the next field connid should show only those connids related to carrid. How this can be achieved in a TMG. If in a module pool, we can write POV or etc. But in TMG, how can we ?
Rgds,
Renjith

See the table maintaince has events ,you can write the code under events.
Reward Points if it is helpful
Thanks
Seshu

How do I access the EC Embedded Controller firmware level with wmi win32?

Hi
I have used the Win32 classes to access the Bios level, model, serial and asset number
The only data I cannot find is the EC firmware level
I cannot find it in any of the WIN32 classes
WIN32_BIOS
WIN32_BASEBOARD etc
Does anyone know if this accessible through the WIN32 classes?

Maybe this is what you mean. I just copied the code out of WMI Code Creator. Although I downloaded an MS Word document from this link
SMBIOS Support in Windows which has information that you may want to read. The first image below is a table from the document. 2nd image and 3rd image are WMI Code Creator launched Console which is displaying info you may want. I don't know what EC firmware
level is.
Imports System
Imports System.Management
Imports System.Windows.Forms
Namespace WMISample
Public Class MyWMIQuery
Public Overloads Shared Function Main() As Integer
Try
Dim searcher As New ManagementObjectSearcher( _
"root\WMI", _
"SELECT * FROM MS_SystemInformation")
For Each queryObj As ManagementObject in searcher.Get()
Console.WriteLine("-----------------------------------")
Console.WriteLine("MS_SystemInformation instance")
Console.WriteLine("-----------------------------------")
Console.WriteLine("Active: {0}", queryObj("Active"))
Console.WriteLine("BaseBoardManufacturer: {0}", queryObj("BaseBoardManufacturer"))
Console.WriteLine("BaseBoardProduct: {0}", queryObj("BaseBoardProduct"))
Console.WriteLine("BaseBoardVersion: {0}", queryObj("BaseBoardVersion"))
Console.WriteLine("BiosMajorRelease: {0}", queryObj("BiosMajorRelease"))
Console.WriteLine("BiosMinorRelease: {0}", queryObj("BiosMinorRelease"))
Console.WriteLine("BIOSReleaseDate: {0}", queryObj("BIOSReleaseDate"))
Console.WriteLine("BIOSVendor: {0}", queryObj("BIOSVendor"))
Console.WriteLine("BIOSVersion: {0}", queryObj("BIOSVersion"))
Console.WriteLine("ECFirmwareMajorRelease: {0}", queryObj("ECFirmwareMajorRelease"))
Console.WriteLine("ECFirmwareMinorRelease: {0}", queryObj("ECFirmwareMinorRelease"))
Console.WriteLine("InstanceName: {0}", queryObj("InstanceName"))
Console.WriteLine("SystemFamily: {0}", queryObj("SystemFamily"))
Console.WriteLine("SystemManufacturer: {0}", queryObj("SystemManufacturer"))
Console.WriteLine("SystemProductName: {0}", queryObj("SystemProductName"))
Console.WriteLine("SystemSKU: {0}", queryObj("SystemSKU"))
Console.WriteLine("SystemVersion: {0}", queryObj("SystemVersion"))
Next
Catch err As ManagementException
MessageBox.Show("An error occurred while querying for WMI data: " & err.Message)
End Try
End Function
End Class
End Namespace
La vida loca

Sharepoint Internet site with NLB via TMG

I have configured two wfes in NLB, the nlb name is say 'spwebnlb'
Using this name as 'hostheader' I have created a webapplication, so that I can access
http://spwebnlb , I am able to achieve this.
Now the issue is I want this site to be accessed with url
https://www.companyname.com
First thing I added this url in AAM of central admin
I have published the site using TMG
In IIS i have added binding for SSL (in iis host name is spwebnlb)
Now I am not able to access the site it give me error as, it is actulally taking me to /pages/variationroot.aspx
The Web application at https://www.companyname.com could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new
request URL mapping to the intended application.

Hi Rizzk,
According to your description, my understanding is that you cannot access the site after publishing the site via TMG.
For troubleshooting your issue, could you access the site in the Intranet? Please make sure you have extended the web application for internet zone and blinded the internet URL in IIS.
For more information, you can refer to the Video :
http://technet.microsoft.com/en-in/video/configure-an-alternate-access-mapping-in-sharepoint-2010.aspx
Best Regards,
Eric
Eric Tao
TechNet Community Support

WMI filter working for some Windows 7 machines but not for others

I'm trying to use this WMI filter for our Windows 7 64bit machines:
select * from Win32_OperatingSystem where (Caption like "Microsoft Windows 7%") or (Version like "6.1%" and ProductType = "1" and OSArchitecture = "64 ビット") or (OSArchitecture like "64%" and ProductType =
"1")
The reason there are three clauses is that we have machines in United States, Japan, and France. The first clause works for the United States, the second clause works for Japan, and the third clause SHOULD work for France, but doesn't.
I've run the query manually on the French machine using WMITest.exe (http://www.paessler.com/tools/wmitester) and it works. However, when I run a gpresult /r it shows that the GPO is denied
due to the WMI filter.
Why is this happening for French computers only?

..the third clause SHOULD work for France, but doesn't.
I've run the query manually on the French machine using WMITest.exe (http://www.paessler.com/tools/wmitester) and it works. However, when I run a gpresult /r it shows that the GPO is denied
due to the WMI filter.
Why is this happening for French computers only?
just a thought - is it due to localisation of the OS (fr-FR), and maybe the WMITest.exe is not honouring that?
maybe, on a French OS, open CMD, run wmic os get osarchitecture ??
get somebody to give you a screengrab of that - just in case there's something funky going on.
(I don't work with multiple languages, so am not sure if localisation can cause your issue, but from your Japan example it looks like it might do so)
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

DFS replication stopped working and cannot be debugged because WMI repository cannot be accessed

Hello,
two days ago our DFS replication suddendly stopped working sometime around midnight local time. At least this is what our second domain controller is reporting. Event log is flooded with event id 5002 from DFSR. It is unclear what caused this sudden problem
and even worse, how to solve it. First thing I tried was to perform propagation tests. According to propagation report none of them was successful. Creating an integrity report brought me to another problem: It fails with two errors. First it is unable to
connect to the other DC. Second it is unable to access local WMI repository. This is true for both machines.
First I tried to find information on possible problems with WMI. WMIdiag provided a lot of information. However, opinions I found on the net largely disagree whether output from WMIdiag is useful or not. Yet I tried to re-compile .mof files and rebuild the
repository. So far, nothing changed. This is my output from WMIdiag:
34309 13:02:46 (0) ** WMIDiag v2.1 started on Donnerstag, 22. Mai 2014 at 12:49.
34310 13:02:46 (0) **
34311 13:02:46 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
34312 13:02:46 (0) **
34313 13:02:46 (0) ** This script is not supported under any Microsoft standard support program or service.
34314 13:02:46 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
34315 13:02:46 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
34316 13:02:46 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
34317 13:02:46 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
34318 13:02:46 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
34319 13:02:46 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
34320 13:02:46 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
34321 13:02:46 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
34322 13:02:46 (0) ** of the possibility of such damages.
34323 13:02:46 (0) **
34324 13:02:46 (0) **
34325 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34326 13:02:46 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
34327 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34328 13:02:46 (0) **
34329 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34330 13:02:46 (0) ** Windows Server 2008 R2 - Service pack 1 - 64-bit (7601) - User 'COM\ABCDEF' on computer 'DC2'.
34331 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34332 13:02:46 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
34333 13:02:46 (0) ** INFO: => 1 possible incorrect shutdown(s) detected on:
34334 13:02:46 (0) ** - Shutdown on 01 April 2014 10:20:54 (GMT-0).
34335 13:02:46 (0) **
34336 13:02:46 (0) ** System drive: ....................................................................................................... C: (Datenträgernr. 0 Partitionsnr. 1).
34337 13:02:46 (0) ** Drive type: ......................................................................................................... SCSI (Adaptec Array SCSI Disk Device).
34338 13:02:46 (0) ** There are no missing WMI system files: .............................................................................. OK.
34339 13:02:46 (0) ** There are no missing WMI repository files: .......................................................................... OK.
34340 13:02:46 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
34341 13:02:46 (0) ** AFTER running WMIDiag:
34342 13:02:46 (0) ** The WMI repository has a size of: ................................................................................... 26 MB.
34343 13:02:46 (0) ** - Disk free space on 'C:': .......................................................................................... 10665 MB.
34344 13:02:46 (0) ** - INDEX.BTR, 4276224 bytes, 22.05.2014 12:52:30
34345 13:02:46 (0) ** - MAPPING1.MAP, 67248 bytes, 22.05.2014 12:52:30
34346 13:02:46 (0) ** - MAPPING2.MAP, 67168 bytes, 22.05.2014 12:48:33
34347 13:02:46 (0) ** - OBJECTS.DATA, 23126016 bytes, 22.05.2014 12:52:30
34348 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34349 13:02:46 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
34350 13:02:46 (0) ** Windows Firewall Profile: ........................................................................................... DOMAIN.
34351 13:02:46 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
34352 13:02:46 (0) ** => This will prevent any WMI remote connectivity to this computer except
34353 13:02:46 (0) ** if the following three inbound rules are ENABLED and non-BLOCKING:
34354 13:02:46 (0) ** - 'Windows Management Instrumentation (DCOM-In)'
34355 13:02:46 (0) ** - 'Windows Management Instrumentation (WMI-In)'
34356 13:02:46 (0) ** - 'Windows Management Instrumentation (ASync-In)'
34357 13:02:46 (0) ** Verify the reported status for each of these three inbound rules below.
34358 13:02:46 (0) **
34359 13:02:46 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
34360 13:02:46 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
34361 13:02:46 (0) ** - You can adjust the configuration by executing the following command:
34362 13:02:46 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
34363 13:02:46 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
34364 13:02:46 (0) ** You can also enable each individual rule instead of activating the group rule.
34365 13:02:46 (0) **
34366 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34367 13:02:46 (0) ** DCOM Status: ........................................................................................................ OK.
34368 13:02:46 (0) ** WMI registry setup: ................................................................................................. OK.
34369 13:02:46 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!
34370 13:02:46 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
34371 13:02:46 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
34372 13:02:46 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
34373 13:02:46 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
34374 13:02:46 (0) ** this can prevent the service/application to work as expected.
34375 13:02:46 (0) **
34376 13:02:46 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
34377 13:02:46 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
34378 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34379 13:02:46 (0) ** WMI service DCOM setup: ............................................................................................. OK.
34380 13:02:46 (0) ** WMI components DCOM registrations: .................................................................................. OK.
34381 13:02:46 (0) ** WMI ProgID registrations: ........................................................................................... OK.
34382 13:02:46 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
34383 13:02:46 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
34384 13:02:46 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
34385 13:02:46 (2) !! WARNING: Some WMI providers EXE/DLL file(s) are missing: ............................................................ 1 WARNING(S)!
34386 13:02:46 (0) ** - ROOT/MICROSOFTACTIVEDIRECTORY, ReplProv1, replprov.dll
34387 13:02:46 (0) ** => This will make any operations related to the WMI class supported by the provider(s) to fail.
34388 13:02:46 (0) ** This can be due to:
34389 13:02:46 (0) ** - the de-installation of the software.
34390 13:02:46 (0) ** - the deletion of some files.
34391 13:02:46 (0) ** => If the software has been de-installed intentionally, then this information must be
34392 13:02:46 (0) ** removed from the WMI repository. You can use the 'WMIC.EXE' command to remove
34393 13:02:46 (0) ** the provider registration data.
34394 13:02:46 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\MICROSOFTACTIVEDIRECTORY path __Win32Provider Where Name='ReplProv1' DELETE'
34395 13:02:46 (0) ** => If not, you must restore a copy of the missing provider EXE/DLL file(s) as indicated by the path.
34396 13:02:46 (0) ** You can retrieve the missing file from:
34397 13:02:46 (0) ** - A backup.
34398 13:02:46 (0) ** - The Windows CD.
34399 13:02:46 (0) ** - Another Windows installation using the same version and service pack level of the examined system.
34400 13:02:46 (0) ** - The original CD or software package installing this WMI provider.
34401 13:02:46 (0) **
34402 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34403 13:02:46 (0) ** INFO: User Account Control (UAC): ................................................................................... DISABLED.
34404 13:02:46 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
34405 13:02:46 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
34406 13:02:46 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
34407 13:02:46 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
34408 13:02:46 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
34409 13:02:46 (0) **
34410 13:02:46 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
34411 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\ANONYMOUS LOGON' has been REMOVED!
34412 13:02:46 (0) ** - REMOVED ACE:
34413 13:02:46 (0) ** ACEType: &h0
34414 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34415 13:02:46 (0) ** ACEFlags: &h0
34416 13:02:46 (0) ** ACEMask: &h7
34417 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34418 13:02:46 (0) ** DCOM_RIGHT_ACCESS_LOCAL
34419 13:02:46 (0) ** DCOM_RIGHT_ACCESS_REMOTE
34420 13:02:46 (0) **
34421 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34422 13:02:46 (0) ** Removing default security will cause some operations to fail!
34423 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34424 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34425 13:02:46 (0) **
34426 13:02:46 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
34427 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
34428 13:02:46 (0) ** - REMOVED ACE:
34429 13:02:46 (0) ** ACEType: &h0
34430 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34431 13:02:46 (0) ** ACEFlags: &h0
34432 13:02:46 (0) ** ACEMask: &h7
34433 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34434 13:02:46 (0) ** DCOM_RIGHT_ACCESS_LOCAL
34435 13:02:46 (0) ** DCOM_RIGHT_ACCESS_REMOTE
34436 13:02:46 (0) **
34437 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34438 13:02:46 (0) ** Removing default security will cause some operations to fail!
34439 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34440 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34441 13:02:46 (0) **
34442 13:02:46 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
34443 13:02:46 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
34444 13:02:46 (0) ** - REMOVED ACE:
34445 13:02:46 (0) ** ACEType: &h0
34446 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34447 13:02:46 (0) ** ACEFlags: &h0
34448 13:02:46 (0) ** ACEMask: &h7
34449 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34450 13:02:46 (0) ** DCOM_RIGHT_ACCESS_LOCAL
34451 13:02:46 (0) ** DCOM_RIGHT_ACCESS_REMOTE
34452 13:02:46 (0) **
34453 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34454 13:02:46 (0) ** Removing default security will cause some operations to fail!
34455 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34456 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34457 13:02:46 (0) **
34458 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
34459 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
34460 13:02:46 (0) ** - REMOVED ACE:
34461 13:02:46 (0) ** ACEType: &h0
34462 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34463 13:02:46 (0) ** ACEFlags: &h0
34464 13:02:46 (0) ** ACEMask: &h1F
34465 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34466 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34467 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34468 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34469 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34470 13:02:46 (0) **
34471 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34472 13:02:46 (0) ** Removing default security will cause some operations to fail!
34473 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34474 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34475 13:02:46 (0) **
34476 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
34477 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
34478 13:02:46 (0) ** - REMOVED ACE:
34479 13:02:46 (0) ** ACEType: &h0
34480 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34481 13:02:46 (0) ** ACEFlags: &h0
34482 13:02:46 (0) ** ACEMask: &h1F
34483 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34484 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34485 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34486 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34487 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34488 13:02:46 (0) **
34489 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34490 13:02:46 (0) ** Removing default security will cause some operations to fail!
34491 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34492 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34493 13:02:46 (0) **
34494 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
34495 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
34496 13:02:46 (0) ** - REMOVED ACE:
34497 13:02:46 (0) ** ACEType: &h0
34498 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34499 13:02:46 (0) ** ACEFlags: &h0
34500 13:02:46 (0) ** ACEMask: &h1F
34501 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34502 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34503 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34504 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34505 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34506 13:02:46 (0) **
34507 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34508 13:02:46 (0) ** Removing default security will cause some operations to fail!
34509 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34510 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34511 13:02:46 (0) **
34512 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
34513 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
34514 13:02:46 (0) ** - REMOVED ACE:
34515 13:02:46 (0) ** ACEType: &h0
34516 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34517 13:02:46 (0) ** ACEFlags: &h0
34518 13:02:46 (0) ** ACEMask: &h1F
34519 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34520 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34521 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34522 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34523 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34524 13:02:46 (0) **
34525 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34526 13:02:46 (0) ** Removing default security will cause some operations to fail!
34527 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34528 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34529 13:02:46 (0) **
34530 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
34531 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
34532 13:02:46 (0) ** - REMOVED ACE:
34533 13:02:46 (0) ** ACEType: &h0
34534 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34535 13:02:46 (0) ** ACEFlags: &h0
34536 13:02:46 (0) ** ACEMask: &h1F
34537 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34538 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34539 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34540 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34541 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34542 13:02:46 (0) **
34543 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34544 13:02:46 (0) ** Removing default security will cause some operations to fail!
34545 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34546 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34547 13:02:46 (0) **
34548 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
34549 13:02:46 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
34550 13:02:46 (0) ** - REMOVED ACE:
34551 13:02:46 (0) ** ACEType: &h0
34552 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34553 13:02:46 (0) ** ACEFlags: &h0
34554 13:02:46 (0) ** ACEMask: &hB
34555 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34556 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34557 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34558 13:02:46 (0) **
34559 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34560 13:02:46 (0) ** Removing default security will cause some operations to fail!
34561 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34562 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34563 13:02:46 (0) **
34564 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
34565 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
34566 13:02:46 (0) ** - REMOVED ACE:
34567 13:02:46 (0) ** ACEType: &h0
34568 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34569 13:02:46 (0) ** ACEFlags: &h0
34570 13:02:46 (0) ** ACEMask: &h1F
34571 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34572 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34573 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34574 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34575 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34576 13:02:46 (0) **
34577 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34578 13:02:46 (0) ** Removing default security will cause some operations to fail!
34579 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34580 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34581 13:02:46 (0) **
34582 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
34583 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
34584 13:02:46 (0) ** - REMOVED ACE:
34585 13:02:46 (0) ** ACEType: &h0
34586 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34587 13:02:46 (0) ** ACEFlags: &h0
34588 13:02:46 (0) ** ACEMask: &h1F
34589 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34590 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34591 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34592 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34593 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34594 13:02:46 (0) **
34595 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34596 13:02:46 (0) ** Removing default security will cause some operations to fail!
34597 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34598 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34599 13:02:46 (0) **
34600 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
34601 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
34602 13:02:46 (0) ** - REMOVED ACE:
34603 13:02:46 (0) ** ACEType: &h0
34604 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34605 13:02:46 (0) ** ACEFlags: &h0
34606 13:02:46 (0) ** ACEMask: &h1F
34607 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34608 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34609 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34610 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34611 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34612 13:02:46 (0) **
34613 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34614 13:02:46 (0) ** Removing default security will cause some operations to fail!
34615 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34616 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34617 13:02:46 (0) **
34618 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
34619 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED!
34620 13:02:46 (0) ** - REMOVED ACE:
34621 13:02:46 (0) ** ACEType: &h0
34622 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34623 13:02:46 (0) ** ACEFlags: &h0
34624 13:02:46 (0) ** ACEMask: &h1F
34625 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34626 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34627 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34628 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34629 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34630 13:02:46 (0) **
34631 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34632 13:02:46 (0) ** Removing default security will cause some operations to fail!
34633 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34634 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34635 13:02:46 (0) **
34636 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
34637 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\LOCAL SERVICE' has been REMOVED!
34638 13:02:46 (0) ** - REMOVED ACE:
34639 13:02:46 (0) ** ACEType: &h0
34640 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34641 13:02:46 (0) ** ACEFlags: &h0
34642 13:02:46 (0) ** ACEMask: &h1F
34643 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34644 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34645 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34646 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34647 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34648 13:02:46 (0) **
34649 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34650 13:02:46 (0) ** Removing default security will cause some operations to fail!
34651 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34652 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34653 13:02:46 (0) **
34654 13:02:46 (0) **
34655 13:02:46 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
34656 13:02:46 (0) ** DCOM security error(s) detected: .................................................................................... 14.
34657 13:02:46 (0) ** WMI security warning(s) detected: ................................................................................... 0.
34658 13:02:46 (0) ** WMI security error(s) detected: ..................................................................................... 0.
34659 13:02:46 (0) **
34660 13:02:46 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
34661 13:02:46 (0) ** Overall WMI security status: ........................................................................................ OK.
34662 13:02:46 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
34663 13:02:46 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
34664 13:02:46 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
34665 13:02:46 (0) ** 'select * from MSFT_SCMEventLogEvent'
34666 13:02:46 (0) **
34667 13:02:46 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
34668 13:02:46 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
34669 13:02:46 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
34670 13:02:46 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
34671 13:02:46 (0) ** - ROOT/SERVICEMODEL.
34672 13:02:46 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
34673 13:02:46 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
34674 13:02:46 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
34675 13:02:46 (0) ** i.e. 'WMIC.EXE /NODE:"ISWDC2" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
34676 13:02:46 (0) **
34677 13:02:46 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
34678 13:02:46 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
34679 13:02:46 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 32 ERROR(S)!
34680 13:02:46 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34681 13:02:46 (0) ** MOF Registration: ''
34682 13:02:46 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34683 13:02:46 (0) ** MOF Registration: ''
34684 13:02:46 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34685 13:02:46 (0) ** MOF Registration: ''
34686 13:02:46 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34687 13:02:46 (0) ** MOF Registration: ''
34688 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_BITS_BITSNetUtilization, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34689 13:02:46 (0) ** MOF Registration: ''
34690 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_BITS_BITSNetUtilization, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34691 13:02:46 (0) ** MOF Registration: ''
34692 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34693 13:02:46 (0) ** MOF Registration: ''
34694 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34695 13:02:46 (0) ** MOF Registration: ''
34696 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34697 13:02:46 (0) ** MOF Registration: ''
34698 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34699 13:02:46 (0) ** MOF Registration: ''
34700 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34701 13:02:46 (0) ** MOF Registration: ''
34702 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34703 13:02:46 (0) ** MOF Registration: ''
34704 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34705 13:02:46 (0) ** MOF Registration: ''
34706 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34707 13:02:46 (0) ** MOF Registration: ''
34708 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34709 13:02:46 (0) ** MOF Registration: ''
34710 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34711 13:02:46 (0) ** MOF Registration: ''
34712 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34713 13:02:46 (0) ** MOF Registration: ''
34714 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34715 13:02:46 (0) ** MOF Registration: ''
34716 13:02:46 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34717 13:02:46 (0) ** MOF Registration: ''
34718 13:02:46 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34719 13:02:46 (0) ** MOF Registration: ''
34720 13:02:46 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34721 13:02:46 (0) ** MOF Registration: ''
34722 13:02:46 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34723 13:02:46 (0) ** MOF Registration: ''
34724 13:02:46 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34725 13:02:46 (0) ** MOF Registration: ''
34726 13:02:46 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34727 13:02:46 (0) ** MOF Registration: ''
34728 13:02:46 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34729 13:02:46 (0) ** MOF Registration: ''
34730 13:02:46 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34731 13:02:46 (0) ** MOF Registration: ''
34732 13:02:46 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34733 13:02:46 (0) ** MOF Registration: ''
34734 13:02:46 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34735 13:02:46 (0) ** MOF Registration: ''
34736 13:02:46 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34737 13:02:46 (0) ** MOF Registration: ''
34738 13:02:46 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34739 13:02:46 (0) ** MOF Registration: ''
34740 13:02:46 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34741 13:02:46 (0) ** MOF Registration: ''
34742 13:02:46 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34743 13:02:46 (0) ** MOF Registration: ''
34744 13:02:46 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
34745 13:02:46 (0) ** a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
34746 13:02:46 (0) ** You can refresh the WMI class provider buffer with the following command:
34747 13:02:46 (0) **
34748 13:02:46 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF'
34749 13:02:46 (0) **
34750 13:02:46 (0) ** WMI MOF representations: ............................................................................................ OK.
34751 13:02:46 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
34752 13:02:46 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
34753 13:02:46 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
34754 13:02:46 (2) !! WARNING: WMI GET VALUE operation errors reported: ................................................................... 5 WARNING(S)!
34755 13:02:46 (0) ** - Root, Instance: __EventConsumerProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
34756 13:02:46 (0) ** - Root, Instance: __EventProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
34757 13:02:46 (0) ** - Root, Instance: __EventSinkCacheControl=@, Property: ClearAfter='00000000000015.000000:000' (Expected default='00000000000230.000000:000').
34758 13:02:46 (0) ** - Root, Instance: __ObjectProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
34759 13:02:46 (0) ** - Root, Instance: __PropertyProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
34760 13:02:46 (0) **
34761 13:02:46 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
34762 13:02:46 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
34763 13:02:46 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
34764 13:02:46 (0) ** WMI static instances retrieved: ..................................................................................... 1822.
34765 13:02:46 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
34766 13:02:46 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
34767 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34768 13:02:46 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
34769 13:02:46 (0) ** DCOM: ............................................................................................................. 0.
34770 13:02:46 (0) ** WINMGMT: .......................................................................................................... 0.
34771 13:02:46 (0) ** WMIADAPTER: ....................................................................................................... 0.
34772 13:02:46 (0) **
34773 13:02:46 (0) ** # of additional Event Log events AFTER WMIDiag execution:
34774 13:02:46 (0) ** DCOM: ............................................................................................................. 0.
34775 13:02:46 (0) ** WINMGMT: .......................................................................................................... 0.
34776 13:02:46 (0) ** WMIADAPTER: ....................................................................................................... 0.
34777 13:02:46 (0) **
34778 13:02:46 (0) ** 32 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
34779 13:02:46 (0) ** => This error is typically a WMI error. This WMI error is due to:
34780 13:02:46 (0) ** - a missing WMI class definition or object.
34781 13:02:46 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
34782 13:02:46 (0) ** You can correct the missing class definitions by:
34783 13:02:46 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
34784 13:02:46 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
34785 13:02:46 (0) ** (This list can be built on a similar and working WMI Windows installation)
34786 13:02:46 (0) ** The following command line must be used:
34787 13:02:46 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
34788 13:02:46 (0) ** Note: When a WMI performance class is missing, you can manually resynchronize performance counters
34789 13:02:46 (0) ** with WMI by starting the ADAP process.
34790 13:02:46 (0) ** - a WMI repository corruption.
34791 13:02:46 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
34792 13:02:46 (0) ** to validate the WMI repository operations.
34793 13:02:46 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
34794 13:02:46 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
34795 13:02:46 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
34796 13:02:46 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
34797 13:02:46 (0) ** the WMI repository must be reconstructed.
34798 13:02:46 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
34799 13:02:46 (0) ** otherwise some applications may fail after the reconstruction.
34800 13:02:46 (0) ** This can be achieved with the following command:
34801 13:02:46 (0) ** i.e. 'WMIDiag ShowMOFErrors'
34802 13:02:46 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
34803 13:02:46 (0) ** ALL fixes previously mentioned.
34804 13:02:46 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
34805 13:02:46 (0) **
34806 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34807 13:02:46 (0) ** WMI Registry key setup: ............................................................................................. OK.
34808 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34809 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34810 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34811 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34812 13:02:46 (0) **
34813 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34814 13:02:46 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
34815 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34816 13:02:46 (0) **
34817 13:02:46 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\ABCDEF\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2K8R2.SRV.SP1.64_ISWDC2_2014.05.22_12.49.13.LOG' for details.
34818 13:02:46 (0) **
34819 13:02:46 (0) ** WMIDiag v2.1 ended on Donnerstag, 22. Mai 2014 at 13:02 (W:89 E:52 S:1).
There are a lot of error in the report and I don't know, whether they are relevant or how to solve them. To my current knowledge, I need to solve at least some of them so that I can access the local WMI repository again and get replication back working.
But after hours of research I am stuck. Any hints are greatly appreciated.
Regards,
Oliver

I don't know why, but soon after posting this, I found a solution to the problem. The WMI part was solved in this thread:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/953be9ef-e9e3-4885-a5c4-47fc475ba562/dfs-is-not-working-anymore?forum=winserverfiles
The relevant portion is this:
Open a CMD prompt in %windir%\system32\wbem
mofcomp dfsrprovs.mof
net stop winmgmt
net start winmgmt
net start iphlpsvc
net stop dfsr
net start dfsr
I don't know why recompiling of all mof did not solve the problem, but the solution above did. Restarting the DCs solved the communication issue. I don't know why the primary DC forgot about the WMI DFS provider or why communication failed. However, it is
working again, it seems.

SCCM 2012 R2 CU2 Can't Edit WMI Query Code in Report Builder

I first posted this in the SCCM but the issue is not solved so I thought I'd try here in the SQL Reporting forum. Original thread here: http://social.technet.microsoft.com/Forums/en-US/b0a6ca3d-7471-4b49-8447-7403a65c2ec0/sccm-2012-r2-cu2-cant-edit-wmi-query-code-in-sccm-reports?forum=configmanagergeneral
I'll repost info here to make this easier.....
I built a new SCCM 2012 R2 CU2 suite on Server 2012 R2. This also uses SQL 2012 SP1 CU6. This suite has 4 servers: site server, two for WSUS and secondary DPs, and SQL. This problem is true for the built in reports and my custom reports. Our SQL guy has
been helping me a lot but we've gotten nowhere. I can run a report. I can open one in edit mode after it prompts me for credentials. It loads Report Builder 3.0. But when I go to a dataset/query, enter credentials, and try to open it, I get a popup that
says "Unable to connect to data source. 'AutoGen_5C6358F2_yayak..." When I click on details it says "The target principal name is incorrect. A connection was succesfully established with the server, but then an error occurred during the login
process. (SSL Provider, error: 0 -The target principal name is incorrect.)" In SQL Reporting Services Config Manager the paths for Web Service URL is
http://ip.ip.ip.ip:80/ReportServer_SC01 and for Report Manager URL:
http://ip.ip.ip.ip:80/Reports_SC01. A domain account is used to login. This happens when you r-click a dataset and select query to edit the code of a dataset, ie, when query designer tries to open up. It happens
in both Admin Console and when using the Report Manager URL within SQL SSRS. All other functions of using edit mode of a report work fine.
Ben JohnsonWY

When I do that, browse is dimmed out.
But, if I deselect "create a data set" and click "choose an existing dataset in this report..." there is no data connection at the end.
But if I don't use report builder and instead use IE to browse to my ConfigMgr_ABC, I do see the connection at the end: {123...}.
This problem is on a network that is not on the 'net, so it's hard to do screen shots, so I'll reproduce this problem step by step:
I pick a report to edit, it doesn't matter which one.
If I try it in Admin Console, I right-click, Edit the report, it asks me for a login, I login, then I get a popup that says "Cannot continue. The application is improperly formatted. Contact the vendor for assistance. I click the Details button and
get a long set of text but the key part is "Your web browser settings do not allow you to run signed applications." This msg didn't appear before, so something changed, so I will investigate. I think it used to give a SPN error.
If I use IE within report builder and navigate to whatever report, click open, everything works, except, when I click on Dataset0 (the key one I normally need to edit), click query, it prompts me for a login and no matter which one I use, i get a popup that
says "unable to connect to data source 'AutoGen_123...'". If I click details I get "the targe principal name is incorrect. A connection was successfully established with the server, but then an error occurred during the login process. (provider:
SSL Provider 0-The target principal name is incorrect.)
Ben JohnsonWY

Kerberos double hop works internally, but not when published via TMG

Hi all,
Have 2 x IIS 8.5 servers internally with .net applications on them
The IIS servers have been configured to use a domain account for their apppool... and credentials are pass successfully from the front end server to the back end server.
When publishing the front-end server via TMG, the front-end web pages show up fine, but the delegated credentials aren't passed to the "back end" pages and a 401 - unauthorised error is presented.
The TMG computer account has the front end and back end http SPN's defined for delegation in its AD account properties.
Is this expected ? is this a limitation of TMG ? or have I simply done something incorrect ?

Hi,
Please check the following article to see if you missed anything.
About Kerberos constrained delegation
https://technet.microsoft.com/en-us/library/cc995228.aspx
Best Regards,
Joyce
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Apple Mail on Macbook via windows domain network and microsoft TMG

Hi folks.
We run a windows network with server 2008 tmg, dcs, and exchange 2007.
We have a few mac clients on our internal network. They log on locally but have all the correct network settings etc for proxy, network and internet access. Everything works fine through TMG including apple mail to our exchange server, and web browsing etc.
The one thing that isn't working is apple mail to other mail providers. Specifically Gmail.
I've created an access rule for testing purposes to allow all outbound traffic from a macbook pro. It still doesn't work, with the following being the only error:
Denied Connection RHSTMG 21/05/2010 10:27:07
Log type: Firewall service
Status: An ingoing packet was dropped because its destination address does not exist on the system, and no appropriate forwarding interface exists.
Rule: None - see Result Code
Source: Internal (10.1.0.81:5353)
Destination: External (224.0.0.251:5353)
Protocol: Unidentified IP Traffic (UDP:5353)
Additional information
•Number of bytes sent: 0 Number of bytes received: 0
•Processing time: 0ms Original Client IP: 10.1.0.81
Someone on another (microsoft) forum said this:
224.0.0.251:5353 is RendezVous protocol, which is used by Mac OS for locating services. it is multicast protocol and it's only purpose is locating things.most it has nothing to do with Google Mail.
The mac has entirely unrestricted access to everywhere (in theory).
Gmail account through windows 7 client using outlook is fine by the way.
Nothing else is denied or refused when looking at the live logging.
Any help with this would be great.
Thanks
Dave

I had this problem too, but I found a post burried on the web that said to add " p06- " (without quotes) before the imap and smpt server names and that worked:
p06-imap.mail.me.com
p06-smtp.mail.me.com
Everything stays checked, SSL for both, authentication and use same username and password checked.

TMG - 0x80090325 -Certificate Chain was issued by an authority that is not trusted

Hello,
I am having some problems with testing a OWA (SSL) rule. I get that message.
The TMG belongs to the domain and therefore as far as I know it gets the root certificate of my CA (I have deployed a Enterprise CA for my domain).
That is why I don't understand the message: "...that is not trusted."
The exact message:
Testing https://mail.mydomain.eu/owa
Category: Destination server certificate error
Error details: 0x80090325 - The certificate chain was issued by an authority that is not trusted
Thanks in advance!
Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)

Thanks Keith for your reply and apologies for the delay in my answer.
I coud not wait and I reinstalled the whole machine (W28k R2 + TMG 2010) . I suppose I am still a bad troubleshooter, I have experience setting up ISA, TMG, PKI, Active directory but to a certain extent.
1. Yes, I saw it when hitting the button "Test Rule" in the Publising rule in the TMG machine.
2. No, it did not work in this implementation but it has worked in others, this is not difficult to set up, until now, hehe.
3. You said: "...If you are seeing it when running "Test Rule" then it simply means that TMG does not trust something about the certificate that is on your Exchange Server...."
But the certificates are auto-enrolled, and when I saw the details of the certificates they all are "valid" , there is a "valid" message.
4. You wrote: "...Easiest way see everything is create an access rule that allows traffic from the LocalHost of TMG to the CAS and open up a web browser. Does the web browser complain?..."
But as I said, I re-installed the whole thing because nobody jumped in here , and I needed to move forward, I hope you understand.
5. S Guna kindly proposed this:
If you are using internal CA,
You need to import the Root CA certificate to TMG servers.
Import Private Key of the certificate to Server personal
Create a Exchange publishing Rule and Point the lisitner to the Correct certificate.
Since you are using internal CA, You need to import the Root CA certificate to all the client browers from where you are accessing OWA
But I think I do not have to perform any of those tasks, although I am not an expert but have worked with Certificate for one year or so.
Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)

TMG Error code 500 Certificate chain was issued by an authority that is not trusted

Hello colleagues
I have site https://site.domain.ru:9510/pmpsvc
In site work: http://imgur.com/2cQ6vlF
I publish this site through TMG 2010, but I have error:
500 Internal Server Error. The certificate chain was issued by an authority that is not trusted (-2146893019).
On TMG server via MMC I imported certificate to:
http://imgur.com/eYqjrQg and reboot TMG server, but problem is not solved.
Maybe someone solved this problem?
Thanks.

This is because your certificate is unable to reach CA to verify the certificate
Ensure your TMG can reach the certificate authority
Import Root CA certificate to Trusted Root certificate authority in CertMGR
If you are using intermediate CA then import the intermediate CA certificate to intermediate CA in certmgr
Thanks, but I use certificate "*.domain.ru" and another https sites without port 9510 works fine. Maybe problem with site on TMG because problem with certificate on web-server (about Certificate error) -
http://imgur.com/2cQ6vlF ??

How do I change the assigned site code on a REMOTE client via WMI (C#)?

Hi
I was wondering if it is possible to change the site code on a client remotely via WMI. I have found one or two links to this, eg
http://msdn.microsoft.com/en-us/library/jj874135.aspx
and
http://social.technet.microsoft.com/Forums/systemcenter/en-US/67b671bb-4819-4e7a-a4f6-6cb7ded17722/sccm-2007-change-assigned-site-code-on-clients?forum=configmgrgeneral
However none of these will allow me to change it remotely directly from my machine. I have written a tool which fixes many issues but having difficulty with this one. In the past I have even resorted to copying a script remotely to an affected machine then
setting a remote scheduled task which executes the script. This was effective but very dirty! I find it difficult to believe there is no way to do this directly but can't seem to find anything suggesting it is possible.
Before anyone replies with a 'what are you trying to achieve...' type answer, I have a similar situation to that of the guy in the second link but I would like something more instant.
Many thanks

psexec or winrm will allow you to do this.
Jason | http://blog.configmgrftw.com

WMI Performance counters not shown in SCOM Performance view

Hi,
We're unable to see %CPU usage, avg cpu queue length and many other WMI counters on a Performance View for one of our servers.
- The agent is displayed as healthy.
- We are getting data from counters generated by script.
- WMI counters are shown as enabled.
- We're able to see the counters locally on server manager, on performance counters.
- we have run lodctr /R, without success.
- no alerts on the scom agent or server.
- no overrides for these counters exist.
So definitely it looks like the WMI infrastructure is working ok but somehow data is not being sent to the server. Any hints on debugging this issue?
Thanks in advance

Ops Manager, Ops DW, or both? If performance collection is ENABLED for this server, and it's a W2K8 box, and you can see the perf in perf monitor on the server, then you should look to see if other performance is missing. If there are no performance
counters being collected, then you can do a few things, but before doing that, do some spot checking.
Is this rule enabled? Did someone override disable it? If enabled, and no overrides, then create a view (my views or whatever that custom workspace is) targetting the generic class of "said" target for the collection rule. Do you see any
computers listed? How many computers are listed? Jot that down. Go to discovered inventory in the monitoring pane, and change scope to the targeted class for the collection rule. Count what is returned, do the number of servers returned
match?
If you have the same number of green healthy objects in both the custom view and the discovered inventory scope, then you are good, if there are a few missing, you need to troubleshoot those agents.
If you are missing all of them, you probably have a problem with your RMS/SQL, which means you have to start traces on SQL and or at the very least look at the ops manager event log on the rms.
So, back to the "missing a few" scenario. You could start to do logging, etc, but instead of that, reinstall the agent on one of the machines not showing up in both views. Wait a few hours. Check the views again, and keep an eye on the
ops manager event log on that sick agent. Increase the size of the log file, if you have too, so you don't over right events.
After a few hours if it's not showing up, you can either start down the path of enabling tracing on the agent (there are kbs on how to turn this on, and the logs are not hard to go through), or you can uninstall the agent. Run cleanmom on the box.
Reinstall the agent.
I would perform the repair, clean mom, before I troubleshoot the agent, but that's just me. Keep in mind, any data that is collected and or queued will be lost when you do the clean mom. But since you have no data as it is, no real loss.
While the agent is showing up in the console, and before you start down the previous steps, I would verify that you have events collected as well (another query) and stop a service on the box that is supposed to be monitored, see if it triggers and alert
and a state change. Also peek at the RMS ops manager event log, you might have some SQL problems.
Good luck.
Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

Set Scope for Virtual Machine in 2012 R2 WMI v2 Namespace

Basically, I want to know how to set the scope for a hyper-v vm in Server 2012 R2 so users see only the specific vm's assigned to them. I work at an academic institution, we intend to upgrade our 2008 R2 servers to 2012 R2 but before we can do that we
need our vm creation script to work properly. In older editions that have the WMI v1 namespace it used to be to set the scope for a vm you did so by modifying Msvm_VirtualSystemGlobalSettingData.ScopeOfResidence. In the WMI v2 namespace Msvm_VirtualSystemGlobalSettingData
has been removed and most of its features have been placed in Msvm_VirtualSystemSettingData. ScopeOfResidence however is not in there and I can't find it or anything that sounds the same in any of the virtual system classes. Below is the unedited portion of
the old script I am having trouble converting to the v2 namespace. Someone please help, I need this working by the end of the month or I am going to have to abandon the server upgrade entirely.
# Set Scope!
$VM_Service = get-wmiobject -namespace root\virtualization Msvm_VirtualSystemManagementService
$ListofVMs = get-wmiobject -namespace root\virtualization Msvm_ComputerSystem -filter "ElementName <> Name " | `
    where { $_.ElementName -like $vmName }
foreach ($VirtualMachine in $ListofVMs) {
        if ($VirtualMachine -ne $Null)
        $VMGlobalSetting = get-wmiobject -namespace root\virtualization Msvm_VirtualSystemGlobalSettingData | where `
           { $_.ElementName -like "*$($VirtualMachine.ElementName)*" }
         $VMGlobalSetting.ScopeOfResidence = $scope
         $VM_Service.ModifyVirtualSystem($VirtualMachine.__PATH, $VMGlobalSetting.psbase.Gettext(1))
Write-Host "Virtual Machine" $vmName "Added to Scope" $scope
# End of Set Scope

HI,
I have the exact same problem, and it totally prevents me from finishing my virtual environment.
I would like to be able to move some VM in specific scopes in order to apply access right on them, but nothing in the V2 tree seems to help...Is there an other way to do it on Hyper-V Server 2012 ?
Also, all modification using azman.msc are totally useless, and adding new groups and/or user in the Administrator role doesn't help.
Any advice will be welcome !

How to create a WMI filter in order to apply to machines that have Skype already installed with deploying a newer version of Skype

Hi there,
I was wondering whether anybody could tell me how to create a WMI filter in order to apply to machines that have Skype already installed with deploying a newer version of Skype.
Your help would be much appreciated.
Many thanks,
Timbuctoo

Hi,
To create a WMI filter
1.In the Group Policy Management Console (GPMC) console tree, right-click
WMI Filters in the forest and domain in which you want to create a WMI filter.
2.Click
New .
3.In the
New WMI Filter dialog box, type a name for the new WMI Filter in the
Name box, and type a description of the filter in the Description box.
4.Click
Add .
5.In the
WMI Query dialog box, either leave the default namespace (root\CIMv2) or enter another namespace by doing one of the following:
◦ In the
Namespace box, type the name of the namespace that you want to use for the WMI query.
◦ Click
Browse , select a namespace from the list, and then click
OK .
6.Type a WMI query in the
Query box, and then click OK .
7.To add more queries, repeat Steps 4 through 6 to add each query.
8.After adding all queries, click
Save .
In the Query box, type the following WMI query:
Select * from Win32_Product where Name LIKE “%Skype%”
Best Regards,
Erin

WMI to TMG

Similar Messages

Maybe you are looking for