Cannot connect to Domain
Hello,
We are trying to connect to Domain, Domain name is set up on the server.
We ping the IP and its working, but when we try to join the domain the following errors pop up
An Active Directory Domain Controller (AD DC) for the domain "proximity" could not be contacted. Ensure that the domain name is typed correctly.
Any idea please?
If you have the ldp.exe tool installed on the device you can query ports 389 & 3268 to make sure they are open and able to reach the DC. If you have a DHCP server in this setup bypass it and try using a PC to DC join (remove all possible issues) DNS
can be an issue but using NSLOOKUP can quickly remove that from the equation. Make sure you have the required AD ports open between point A and B (Link for that below) Also If you have IPSEC in your enviroment this can be an issue. Needless to say it can be
a lot of things but if you need a simple method to start id do this:
Ensure all required AD ports are open and listening.
Ensure all required services (netlogon, task scheduler, etc) are enabled and the time is properly set on the device.
Ensure my NIC settings are configured correctly & I can resolve DNS using NSLOOKUP and typing the FQDN for the domain.
Ensure my IPSEC, firewall, etc is configured as needed.
AD Ports:
http://msdn.microsoft.com/en-us/library/dd772723(v=ws.10).aspx
DNS Issue Blog:
http://blogs.msdn.com/b/deva/archive/2013/03/23/dns-issue-cannot-join-domain-windows-server-2008-r2-server.aspx
Similar Messages
-
hi, I'm using windows server 2012 R2 and I was Just wondering how to make the Remote Desktop enable connection through domain\administrator before actually creating the domain... In other words, I wanted to create an Active Directory Domain User and connect
to the server from the RDP. The problem is that I can only connect through the RDP considering that I'm using Windows Azure, so the physical server isn't actually sitting on my desk... Anyway when I create an AD DS the system automatically reboots and I'm
not able to connect to it anymore, so all I need to do right now is enable somehow the Remote Desktop Services to connect through "Domain\Administrator" before I actually create the AD DS and assign it to my server so that when the system reboots
and I open the RDP I can connect to the server.
Thanks in advance.Hi,
Thank you for posting in Windows Server Forum.
As per your comment, it seems that you are managing the server with .RDP file. I can suggest you to run
"Remote Desktop Connection Manager” for maintaining server. With that you can specify the credential for domain\administrator and when you setup the AD DS, after that you can open the connection through domain\administrator and not as local user.
Hope it helps!
Thanks,
Dharmesh -
Windows 8.1 Pro Cannot Connect to Domain Controllers through Wi-Fi
I have a domain joined Surface 2 Pro running 8.1 Pro Update that is suddenly unable to connect to the domain controllers on the local network. The machine is fully patched. I'm guessing that it is some network level security issue because the wi-fi is working:
It has no trouble connecting to my Wi-Fi hotspot on my phone.
It has no trouble connecting to other Wi-Fi at coffee shops etc.
It is connecting to my home Wi-Fi and gets an address from DHCP on the domain controllers, but can't ping the DCs, access the DCs through remote desktop even using their IP address.
It can ping the router and ping systems on the internet using their IP address rather than hostname.
I can fully access internet systems if I point it at DNS on the router but still cannot access internal systems by name or IP address.
The Wi-Fi network shows as a public network rather than a domain.
It will work fine when it is docked and using the dock's ethernet adapter.
If I use VPN to loop back through my router then I am able to fully access local systems.
None of the other systems on the network are experiencing the same issue.
I have tried the following which didn't work:
Switched off the Windows Firewall on the Windows 8.1 system and a domain controller.
Network Troubleshooting - which told me that the network seems OK but the DNS servers are not responding.
Uninstalling the Wi-Fi device and restarting the system to re-install it.
Resetting TCP/IP.
I am not aware of any changes, but the system did install System Hardware Update 8/07/2014 (again!) but I can't recall if that was when the problem started or was just a coincidence.
Any suggestions?
Thanks,
Richard
Richard-FHi Richard,
Apologize for my slow understanding.
I thought as it could obtain IP address from the DC, it should have connections between them.
For the current situation, you may take a try to disable the firewall on the DC, then check the port that used by AD environment is all available,
Active Directory and Active Directory Domain Services Port Requirements, you could take use of this tool:
PortQryUI - User Interface for the PortQry Command Line Port Scanner
If all available and issue still insists, then issue here seems to be restricted with the wireless router. You may try to contact the router side and see if they could offer any further useful information regarding this situation.
Best regards
Michael Shao
TechNet Community Support -
Cannot Connect to Domain Through Wireless Connection
Hello TechNet Gurus,
As the title suggests, I am having issues connecting to my domain through a wireless connection. I am running Windows Server 2008 R2 (Data Center and Enterprise) to build my understanding of server administration to supplement my undergraduate
coursework (B.S. Computer Engineering & Cyber Security minor). So far I have a working domain controller attached to a switch that I re-purposed from an old WRT54G Linksys router. In turn, the switch is attached to a WRT54GS Linksys router.
When connected through physical media, the domain controller works as expected. I can connect to the domain from two personal laptops running Windows 7 Professional and from two virtual environments running Windows 7 Enterprise. Through these connections, I
can divvy out group policy, access network drives, and other services successfully. However, I attempted to connect wireless, and when I do, I continually get an error indicating that my username/password is incorrect. I carefully re-input the login information
(over-and-over), and I even recreated the user/computer objects. All to no avail.
After a couple of days of research between classes, homework, and work, I found some promising tips:
Added the following entry to the registry for the local machine: %comspec% /c netsh wlan connect name="JBnetwork"
Added the following local group policy (using gpedit.msc): Computer Configuration\Policies\Administrative templates\System\Logon\Always wait for the network at computer startup and logon
Unfortunately, the above tips have not resolved the issue. From what I understand, the issue stems from the order that the wireless software and domain authenticate. I have also read that this may purely be a networking issue that is not directly related
to Active Directory or Windows 7 configurations. Whatever the situation is, this has me completely stumped and I could use some expert advice.
This is my ipconfig, for the reference:
Connection-specific DNS Suffix . : jbnetwork.local
Description . . . . . . . . . . . : Broadcom 802.11n Network Adapter
Physical Address. . . . . . . . . : 88-9F-FA-88-FA-44
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::18d8:7f74:26a0:c429%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.14(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, August 05, 2014 10:08:35 PM
Lease Expires . . . . . . . . . . : Wednesday, August 06, 2014 10:08:34 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.3
DHCPv6 IAID . . . . . . . . . . . : 294166522
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-1E-03-7F-88-9F-FA-88-FA-44
Thanks to anyone who can help!@Zanderol24,
Thanks for following up with me. I completely forgot about this post because I was able to figure out a solution by poking around in Group Policy.
The issue was a pretty simple fix. I tweaked the wireless policy a bit: Computer Configuration > Policies > Windows Settings > Security Settings > Wireless Network (IEEE 802.11) Policies.
Thanks again! -
Domain users cannot connect to the network folders when logged in via rds remote apps
Hi,
recently I setup an RDS farm for remote apps on server 2012 r2.
all users can connect to the apps published. no problems there.
but when users connect via rds they cannot connect to the networkfolders and cannot store the resultance of there work (docx and xlsx files)
all users are normally connected to the networkfolders using a small login batch file handing down the unc path needed. when I log in as domain admin, also using a login batch, connections are setup correctly. It seems to me to be an security issue on the
rds session host.
how to alter this?
greetz, Fons
Fons system and network engineer Balie AmsterdamHi,
Thank you for posting in Windows Server Forum.
We use WMI to communicate with the RDSH server. Various issues can cause WMI to deny access or return error codes. Here's a few things you can try:
1. Check if the "TS Web Access Computers" security group on the RDSH server has incorrect permissions in DCOM and/or WMI:
For checking DCOM security settings:
1. Start the Component Services MMC snapin
2. Navigate to Component Services -> Computers -> My Computer
3. Right-click on My Computer and select properties
4. Go to the COM Security tab
5. Under Access Permissions, click the Edit Limits button
6. Ensure that TS Web Access Computers is in the list, with all of the permissions set to “allow”.
7. Under Launch and Activation Permissions, click the Edit Limits button
8. Ensure that TS Web Access Computers is in the list, with all of the permissions set to “allow”.
For checking WMI security settings:
1. Start the WMI Control MMC snapin
2. Right-click the WMI Control node and select properties
3. Go to the Security tab
4. Navigate to Root->CIMV2->TerminalServices
5. With TerminalServices selected, click the Security button
6. Ensure that TS Web Access Computers is in the list with Execute Methods, Enable Account, and Remote Enable set to "allow"
2. Verify the RD Session Host server's firewall allows WMI calls.
3. Verify that the RD Connection Broker hasn't lost its trust relationship with the domain.
4. See if non-RDS related WMI calls can be successfully made to the RDSH server. This can help differentiate between a general WMI issue and an issue calling the RDS WMI provider.
(Quoted from following thread.)
RemoteApp Source not working from RDWeb
http://social.technet.microsoft.com/Forums/windowsserver/en-US/173d4546-e12f-47c1-ac66-8b4f69826892/remoteapp-source-not-working-from-rdweb?forum=winserverTS
Hope it helps!
Thanks.
Dharmesh Solanki -
Hi All,
I am trying to install informatica 9.1 HF 2 connecting to 11g DB.
when installing Informatica, I am at the DOMAIN CREATION windows and inputting the DB connect details and for some reason, it cannot connect to the DB.
The DB is running
any ideas?
the error message states:
THE CONNECTION FAILED: CORRECT THE DATABASE INFO AND TEST THE CONNECTION AGAIN..any help please
thanksYup, that did it.
I actually had been made aware of the patch when I downloaded CF, but for some reason I thought it was difficult to install (I thought that you could only use the installer package if you could open Administrator). IAC I downloaded the appropriate patch file, ran it and Administrator ran. There was something in the install notes about reconfiguring the websites and removing the IIS6 Management feature but I'm not going to fool with anything because right now at least CF is running.
Thanks. -
Cannot connect to one domain via wireless
All of a sudden I cannot connect to my COX pop email account with my Macbook via my wireless router only, either by any email client or web access. Ethernet into the same router is ok. My Powerbook G4 is fine or my Dell PC notebook is fine either connection. I've also tried a neighbors wireless connection with the same result. So far any other of my pop 3 connections are ok. This has seemed to happen after upgrading to 10.5.1. Any ideas out there??
In that case you should try to download and upgrtade the firmware for the router.
This link is where you can download the firmware for the router
Click Here
And please click on this link on how to upgrade the firmware for the router
Click Here
Many thanks,
Akira893
wE dOnt gEt mAd! wE gEt evEn!
^_^ -
PI 7.11: Cannot connect to server using message server:...
Hello Guys,
we make the Application Management for a Customer PI System.
Scenario:
- the SAP Gui Connection to the ABAP Stack is routed via SAPRouter and Works fine.
SAP Gui -> our SAP Router -> VPN Box from Customer -> Firewall Customer -> ABAP Stack PI System
- WebAccess its working fine, the Customer use Webdispatcher on every PI Server...
Browser -> VPN Box from Customer -> Firewall Customer -> Java Stack (Port: 5xx00 btw. 81xx (Webdispatcher))
Problem:
Our Problem ist, we can not proceed the Integration Builder or the ESB, the Java Web Start works fine and open the Logon Screen Correctly -> but i fill the Logon Screen with my User name and Password and press Logon come the follwing Error:
"Cannot connect to server using message server: ms://<hostname>.<domain>:8134/P4"
In the Details from the Error Message:
"<hostname>.<domain>:53404 Reason: com.sap.engine.services.rmi_p4.P4IOException:
Cannot open connection to host: <IP-Adress of Central Instance> and Port: 53404"
The Customer says, the Firewall is open with the IP Adresses and P4 Port but i dont think so...
Can everybody help me, or have tips for me! I have checked a lot of OSS Messages (PI High Availabilty etc... its all correct on the System)
Sorry for my bad English
Best Regards,
MarkusHi Markus,
did you check if the browser is using a proxy? (In this case your scenario unfortunately won't work).
P4-port should generally be routed via a proxy (described in the help.sap.com), but within the PI-Tools(JNLP) the proxy-usage is not implemented. There is even a SAP-note that describes how to check the JavaWebStart-Proxyconfiguration, but this won't help either.
If there is a proxy defined in the browser everything is working fine till you pass the logon-screen but even with the correct "javaws"-settings you won't be able to go on.
(This problem is pretty bad if you do have developers and the SAP-servers seperated because of security issues. I'm hoping that this malfunction will be solved with upcoming patches.)
Solution: Establish a connection without any proxy in between.
E.g.: a terminal server in the same network
It would be helpful to find more people with the same problem to force a fix from SAP for that.
If anyone else is having problems with this, please add a comment to this thread.
Best regards
Christian -
Hello, everyone, my name is rafl
I have a problem with exchange 2013 active sync.
I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
(legacy.domain.com)
the process of moving mailboxes successfully without error.
Access OWA for exchange 2007 and exchange 2013 is running normally
access mail from Outlook running normally
Certificate request has been installed and has no problem with it
The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
user mailboxes are still on exchange 2007 is not problematic.
only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
any ideas for this problem, and what should I check on the exchange server ..?i have run the activesync test connectivity and get some error :
Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 3091 ms.
Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21072 ms.
Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21049 ms.
I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server" -
MSSQL Homogeneous System Copy : SAPINST cannot connect to default database
Hello.
We want to perform a homogeneous system copy, following Note 151603.
We have attached the source DB (RP1) to the destination DB (RD4) following the above mentioned Note.
Now, logged to the server as DOMAIN\rd4adm , we want to execute the SAPINST, as indicated in the Note 683447, but when giving the password for user rd4adm we get a pop up
Cannot connect to R3SVIL\RD4 [SQL Server]Cannot open user default database. Login failed.
R3SVIL is the server. Login is done with windows authentication (connected as domain\rd4adm)
We cannot find a Note descibing this issue and how to fix it, must be something with user : does anybody have suggestion or solution?
Thanks a lot,
DinoHi,
did you apply SAP note 551915 - R/3 won't start after database restore or database copy
also check Note 806925 - SQL Error 4064: Cannot open user default database
regards,
kaushal -
Cannot connect to Session broker server, but can to other servers in Cluster
Hi Everyone,
Hopefully this is the right place to post. Have searched quite a bit through the forums (not all 19000+ pages though), and can't seem to find a similiar issue.
I have also searched the internet and tried all solutions others with a similiar problem have.
This is my problem:
We have two servers running Server 2008 R2, set up as Remote Desktop Servers in a cluster setup.
The session broker is located on the second server (This is an active server which has sessions load balanced to it). There is also a DNS round robin setup
Problem: When sessions are allowed to be load balanced on Server2, then the users cannot connect to the cluster. The round robin seems to still send some sessions to the first server, and these seem to connect fine.
I suspected the issue was with the WMI Respository, and so started. I found a lot of errors, but have been unable to fix them.
I downlaoded the WMIDiag from Microsoft, and here is the report:
48866 15:56:44 (0) ** WMIDiag v2.1 started on 15 April 2015 at 15:48.
48867 15:56:44 (0) **
48868 15:56:44 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
48869 15:56:44 (0) **
48870 15:56:44 (0) ** This script is not supported under any Microsoft standard support program or service.
48871 15:56:44 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
48872 15:56:44 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
48873 15:56:44 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
48874 15:56:44 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
48875 15:56:44 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
48876 15:56:44 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
48877 15:56:44 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
48878 15:56:44 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
48879 15:56:44 (0) ** of the possibility of such damages.
48880 15:56:44 (0) **
48881 15:56:44 (0) **
48882 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48883 15:56:44 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
48884 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48885 15:56:44 (0) **
48886 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48887 15:56:44 (0) ** Windows Server 2008 R2 - Service pack 1 - 64-bit (7601) - User 'MIBCO\CONN.LOMBARD' on computer 'SSCRDS02'.
48888 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48889 15:56:44 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
48890 15:56:44 (0) ** INFO: => 3 possible incorrect shutdown(s) detected on:
48891 15:56:44 (0) ** - Shutdown on 05 December 2014 22:55:28 (GMT-0).
48892 15:56:44 (0) ** - Shutdown on 12 December 2014 06:43:00 (GMT-0).
48893 15:56:44 (0) ** - Shutdown on 27 February 2015 05:19:26 (GMT-0).
48894 15:56:44 (0) **
48895 15:56:44 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #1).
48896 15:56:44 (0) ** Drive type: ......................................................................................................... SCSI (DELL PERC H700 SCSI Disk Device).
48897 15:56:44 (0) ** There are no missing WMI system files: .............................................................................. OK.
48898 15:56:44 (0) ** There are no missing WMI repository files: .......................................................................... OK.
48899 15:56:44 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
48900 15:56:44 (0) ** AFTER running WMIDiag:
48901 15:56:44 (0) ** The WMI repository has a size of: ................................................................................... 26 MB.
48902 15:56:44 (0) ** - Disk free space on 'C:': .......................................................................................... 297281 MB.
48903 15:56:44 (0) ** - INDEX.BTR, 5513216 bytes, 2015/04/15 03:52:21 PM
48904 15:56:44 (0) ** - MAPPING1.MAP, 76804 bytes, 2015/04/15 03:50:51 PM
48905 15:56:44 (0) ** - MAPPING2.MAP, 76804 bytes, 2015/04/15 03:52:21 PM
48906 15:56:44 (0) ** - OBJECTS.DATA, 22036480 bytes, 2015/04/15 03:52:21 PM
48907 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48908 15:56:44 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
48909 15:56:44 (0) ** Windows Firewall Profile: ........................................................................................... DOMAIN.
48910 15:56:44 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
48911 15:56:44 (0) ** => This will prevent any WMI remote connectivity to this computer except
48912 15:56:44 (0) ** if the following three inbound rules are ENABLED and non-BLOCKING:
48913 15:56:44 (0) ** - 'Windows Management Instrumentation (DCOM-In)'
48914 15:56:44 (0) ** - 'Windows Management Instrumentation (WMI-In)'
48915 15:56:44 (0) ** - 'Windows Management Instrumentation (ASync-In)'
48916 15:56:44 (0) ** Verify the reported status for each of these three inbound rules below.
48917 15:56:44 (0) **
48918 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' GROUP rule: ............................................. ENABLED.
48919 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ............................................... ENABLED.
48920 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ ENABLED.
48921 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... ENABLED.
48922 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. ENABLED.
48923 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48924 15:56:44 (0) ** DCOM Status: ........................................................................................................ OK.
48925 15:56:44 (0) ** WMI registry setup: ................................................................................................. OK.
48926 15:56:44 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
48927 15:56:44 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
48928 15:56:44 (0) ** - SMS Agent Host (CCMEXEC, StartMode='Automatic')
48929 15:56:44 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
48930 15:56:44 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
48931 15:56:44 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
48932 15:56:44 (0) ** this can prevent the service/application to work as expected.
48933 15:56:44 (0) **
48934 15:56:44 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
48935 15:56:44 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
48936 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48937 15:56:44 (0) ** WMI service DCOM setup: ............................................................................................. OK.
48938 15:56:44 (0) ** WMI components DCOM registrations: .................................................................................. OK.
48939 15:56:44 (0) ** WMI ProgID registrations: ........................................................................................... OK.
48940 15:56:44 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
48941 15:56:44 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
48942 15:56:44 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
48943 15:56:44 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
48944 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48945 15:56:44 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
48946 15:56:44 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
48947 15:56:44 (0) ** i.e. You can start your scripts or WMIC commands from an elevated command
48948 15:56:44 (0) ** prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
48949 15:56:44 (0) ** selecting 'Run as Administrator'.
48950 15:56:44 (0) ** i.e. You can also execute the WMI scripts or WMIC commands as a task
48951 15:56:44 (0) ** in the Task Scheduler within the right security context.
48952 15:56:44 (0) **
48953 15:56:44 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
48954 15:56:44 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
48955 15:56:44 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
48956 15:56:44 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
48957 15:56:44 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
48958 15:56:44 (0) **
48959 15:56:44 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
48960 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES NOT match corresponding expected trustee rights (Actual->Default)
48961 15:56:44 (0) ** - ACTUAL ACE:
48962 15:56:44 (0) ** ACEType: &h0
48963 15:56:44 (0) ** ACCESS_ALLOWED_ACE_TYPE
48964 15:56:44 (0) ** ACEFlags: &h4
48965 15:56:44 (0) ** NO_PROPAGATE_INHERIT_ACE
48966 15:56:44 (0) ** ACEMask: &hB
48967 15:56:44 (0) ** DCOM_RIGHT_EXECUTE
48968 15:56:44 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
48969 15:56:44 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
48970 15:56:44 (0) ** - EXPECTED ACE:
48971 15:56:44 (0) ** ACEType: &h0
48972 15:56:44 (0) ** ACCESS_ALLOWED_ACE_TYPE
48973 15:56:44 (0) ** ACEFlags: &h0
48974 15:56:44 (0) ** ACEMask: &h1F
48975 15:56:44 (0) ** DCOM_RIGHT_EXECUTE
48976 15:56:44 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
48977 15:56:44 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
48978 15:56:44 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
48979 15:56:44 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
48980 15:56:44 (0) **
48981 15:56:44 (0) ** => The actual ACE has the right(s) '&h14 DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
48982 15:56:44 (0) ** This will cause some operations to fail!
48983 15:56:44 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
48984 15:56:44 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
48985 15:56:44 (0) **
48986 15:56:44 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
48987 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\INTERACTIVE' DOES NOT match corresponding expected trustee rights (Actual->Default)
48988 15:56:44 (0) ** - ACTUAL ACE:
48989 15:56:44 (0) ** ACEType: &h0
48990 15:56:44 (0) ** ACCESS_ALLOWED_ACE_TYPE
48991 15:56:44 (0) ** ACEFlags: &h4
48992 15:56:44 (0) ** NO_PROPAGATE_INHERIT_ACE
48993 15:56:44 (0) ** ACEMask: &hB
48994 15:56:44 (0) ** DCOM_RIGHT_EXECUTE
48995 15:56:44 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
48996 15:56:44 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
48997 15:56:44 (0) ** - EXPECTED ACE:
48998 15:56:44 (0) ** ACEType: &h0
48999 15:56:44 (0) ** ACCESS_ALLOWED_ACE_TYPE
49000 15:56:44 (0) ** ACEFlags: &h0
49001 15:56:44 (0) ** ACEMask: &h1F
49002 15:56:44 (0) ** DCOM_RIGHT_EXECUTE
49003 15:56:44 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
49004 15:56:44 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
49005 15:56:44 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
49006 15:56:44 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
49007 15:56:44 (0) **
49008 15:56:44 (0) ** => The actual ACE has the right(s) '&h14 DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
49009 15:56:44 (0) ** This will cause some operations to fail!
49010 15:56:44 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
49011 15:56:44 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
49012 15:56:44 (0) **
49013 15:56:44 (0) **
49014 15:56:44 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
49015 15:56:44 (0) ** DCOM security error(s) detected: .................................................................................... 2.
49016 15:56:44 (0) ** WMI security warning(s) detected: ................................................................................... 0.
49017 15:56:44 (0) ** WMI security error(s) detected: ..................................................................................... 0.
49018 15:56:44 (0) **
49019 15:56:44 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
49020 15:56:44 (0) ** Overall WMI security status: ........................................................................................ OK.
49021 15:56:44 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
49022 15:56:44 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 5.
49023 15:56:44 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
49024 15:56:44 (0) ** 'select * from MSFT_SCMEventLogEvent'
49025 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49026 15:56:44 (0) ** 'SELECT * FROM __NamespaceCreationEvent'
49027 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49028 15:56:44 (0) ** 'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy_EmbeddedObject"'
49029 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49030 15:56:44 (0) ** 'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy_Config"'
49031 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49032 15:56:44 (0) ** 'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy"'
49033 15:56:44 (0) **
49034 15:56:44 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
49035 15:56:44 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
49036 15:56:44 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
49037 15:56:44 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
49038 15:56:44 (0) ** - ROOT/SERVICEMODEL.
49039 15:56:44 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
49040 15:56:44 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
49041 15:56:44 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
49042 15:56:44 (0) ** i.e. 'WMIC.EXE /NODE:"SSCRDS02" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
49043 15:56:44 (0) **
49044 15:56:44 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
49045 15:56:44 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
49046 15:56:44 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 34 ERROR(S)!
49047 15:56:44 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49048 15:56:44 (0) ** MOF Registration: ''
49049 15:56:44 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49050 15:56:44 (0) ** MOF Registration: ''
49051 15:56:44 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49052 15:56:44 (0) ** MOF Registration: ''
49053 15:56:44 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49054 15:56:44 (0) ** MOF Registration: ''
49055 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49056 15:56:44 (0) ** MOF Registration: ''
49057 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49058 15:56:44 (0) ** MOF Registration: ''
49059 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49060 15:56:44 (0) ** MOF Registration: ''
49061 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49062 15:56:44 (0) ** MOF Registration: ''
49063 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49064 15:56:44 (0) ** MOF Registration: ''
49065 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49066 15:56:44 (0) ** MOF Registration: ''
49067 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49068 15:56:44 (0) ** MOF Registration: ''
49069 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49070 15:56:44 (0) ** MOF Registration: ''
49071 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49072 15:56:44 (0) ** MOF Registration: ''
49073 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49074 15:56:44 (0) ** MOF Registration: ''
49075 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49076 15:56:44 (0) ** MOF Registration: ''
49077 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49078 15:56:44 (0) ** MOF Registration: ''
49079 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49080 15:56:44 (0) ** MOF Registration: ''
49081 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49082 15:56:44 (0) ** MOF Registration: ''
49083 15:56:44 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49084 15:56:44 (0) ** MOF Registration: ''
49085 15:56:44 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49086 15:56:44 (0) ** MOF Registration: ''
49087 15:56:44 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49088 15:56:44 (0) ** MOF Registration: ''
49089 15:56:44 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49090 15:56:44 (0) ** MOF Registration: ''
49091 15:56:44 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49092 15:56:44 (0) ** MOF Registration: ''
49093 15:56:44 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49094 15:56:44 (0) ** MOF Registration: ''
49095 15:56:44 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49096 15:56:44 (0) ** MOF Registration: ''
49097 15:56:44 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49098 15:56:44 (0) ** MOF Registration: ''
49099 15:56:44 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49100 15:56:44 (0) ** MOF Registration: ''
49101 15:56:44 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49102 15:56:44 (0) ** MOF Registration: ''
49103 15:56:44 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49104 15:56:44 (0) ** MOF Registration: ''
49105 15:56:44 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49106 15:56:44 (0) ** MOF Registration: ''
49107 15:56:44 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49108 15:56:44 (0) ** MOF Registration: ''
49109 15:56:44 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49110 15:56:44 (0) ** MOF Registration: ''
49111 15:56:44 (0) ** - root/ccm/LocationServices, ClientInfo, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49112 15:56:44 (0) ** MOF Registration: ''
49113 15:56:44 (0) ** - root/ccm/LocationServices, ClientInfo, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49114 15:56:44 (0) ** MOF Registration: ''
49115 15:56:44 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
49116 15:56:44 (0) ** a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
49117 15:56:44 (0) ** You can refresh the WMI class provider buffer with the following command:
49118 15:56:44 (0) **
49119 15:56:44 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF'
49120 15:56:44 (0) **
49121 15:56:44 (0) ** WMI MOF representations: ............................................................................................ OK.
49122 15:56:44 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
49123 15:56:44 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
49124 15:56:44 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
49125 15:56:44 (2) !! WARNING: WMI GET VALUE operation errors reported: ................................................................... 5 WARNING(S)!
49126 15:56:44 (0) ** - Root, Instance: __EventConsumerProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49127 15:56:44 (0) ** - Root, Instance: __EventProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49128 15:56:44 (0) ** - Root, Instance: __EventSinkCacheControl=@, Property: ClearAfter='00000000000015.000000:000' (Expected default='00000000000230.000000:000').
49129 15:56:44 (0) ** - Root, Instance: __ObjectProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49130 15:56:44 (0) ** - Root, Instance: __PropertyProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49131 15:56:44 (0) **
49132 15:56:44 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
49133 15:56:44 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
49134 15:56:44 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
49135 15:56:44 (0) ** WMI static instances retrieved: ..................................................................................... 6304.
49136 15:56:44 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
49137 15:56:44 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 3.
49138 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49139 15:56:44 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
49140 15:56:44 (0) ** DCOM: ............................................................................................................. 0.
49141 15:56:44 (0) ** WINMGMT: .......................................................................................................... 0.
49142 15:56:44 (0) ** WMIADAPTER: ....................................................................................................... 0.
49143 15:56:44 (0) **
49144 15:56:44 (0) ** # of additional Event Log events AFTER WMIDiag execution:
49145 15:56:44 (0) ** DCOM: ............................................................................................................. 0.
49146 15:56:44 (0) ** WINMGMT: .......................................................................................................... 0.
49147 15:56:44 (0) ** WMIADAPTER: ....................................................................................................... 0.
49148 15:56:44 (0) **
49149 15:56:44 (0) ** 34 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
49150 15:56:44 (0) ** => This error is typically a WMI error. This WMI error is due to:
49151 15:56:44 (0) ** - a missing WMI class definition or object.
49152 15:56:44 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
49153 15:56:44 (0) ** You can correct the missing class definitions by:
49154 15:56:44 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
49155 15:56:44 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
49156 15:56:44 (0) ** (This list can be built on a similar and working WMI Windows installation)
49157 15:56:44 (0) ** The following command line must be used:
49158 15:56:44 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
49159 15:56:44 (0) ** Note: When a WMI performance class is missing, you can manually resynchronize performance counters
49160 15:56:44 (0) ** with WMI by starting the ADAP process.
49161 15:56:44 (0) ** - a WMI repository corruption.
49162 15:56:44 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
49163 15:56:44 (0) ** to validate the WMI repository operations.
49164 15:56:44 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
49165 15:56:44 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
49166 15:56:44 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
49167 15:56:44 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
49168 15:56:44 (0) ** the WMI repository must be reconstructed.
49169 15:56:44 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
49170 15:56:44 (0) ** otherwise some applications may fail after the reconstruction.
49171 15:56:44 (0) ** This can be achieved with the following command:
49172 15:56:44 (0) ** i.e. 'WMIDiag ShowMOFErrors'
49173 15:56:44 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
49174 15:56:44 (0) ** ALL fixes previously mentioned.
49175 15:56:44 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
49176 15:56:44 (0) **
49177 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49178 15:56:44 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
49179 15:56:44 (0) ** INFO: Unexpected registry key value:
49180 15:56:44 (0) ** - Current: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 0
49181 15:56:44 (0) ** - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 1
49182 15:56:44 (0) ** From the command line, the registry configuration can be corrected with the following command:
49183 15:56:44 (0) ** i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft\WBEM\CIMOM" /v "Logging" /t "REG_SZ" /d "1" /f'
49184 15:56:44 (0) **
49185 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49186 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49187 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49188 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49189 15:56:44 (0) **
49190 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49191 15:56:44 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
49192 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49193 15:56:44 (0) **
49194 15:56:44 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\CONN.LOMBARD\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2K8R2.SRV.SP1.64_SSCRDS02_2015.04.15_15.48.25.LOG' for details.
49195 15:56:44 (0) **
49196 15:56:44 (0) ** WMIDiag v2.1 ended on 15 April 2015 at 15:56 (W:110 E:41 S:1).
This seems to be the biggest problem:
48960 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES NOT match corresponding expected trustee rights (Actual->Default)
This seems to be the second biggest error (and there are a few of them):
0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
I have tried:
winmgmt /resyncperf
winmgmt /verifyrepository
winmgmt /salvagerepository
winmgmt /resetrepository
I have also tried registering the mof files with
MOFCOMP <FileName.mof>
Lastly, I even disabled the WMI service, renamed the Repository folder, and had it rebuild the repository.
I got stuck on re registering the 'NT AUTHORITY\SYSTEM' (I think it is in the Components section in Administrative tools), as I could not find clear instructions on exactly how to go about it.
Chkdsk found no errors
Sfc /scannow found no errors
winmgmt /verifyrepository finds no errors.
I'm hoping someone here might be able to steer me in the right direction to get this resolved, as I do not want to rebuild a server that hosts a connection broker and has over 100 user profiles on it, as well as some very annoying and finniky LOB apps installed,
which will have to manually be reinstalled for each profile.Hi,
Here is a blog regarding how to fix WMI issue might be useful to you:
Fixing WMI issues Using Batch Script
http://social.technet.microsoft.com/wiki/contents/articles/6887.fixing-wmi-issues-using-batch-script.aspx
In addition, you mentioned Remote Desktop Servers are in a cluster setup, would you tell us how did you create the cluster?
As far as I know, with RD Connection Broker, we don’t need to create a cluster but just add multiple RD session hosts into one collection, then RD connection Broker would redirect sessions automatically.
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] -
Cannot connect to the phone system. An unidentified error has occurred, Please try again.
Issue: Lync 2013 users with remote call control enabled cannot connect to the phone system. When the user logs into Lync, they see an exclamation in the bottom right corner
with this error.
Error: Cannot connect to the phone system. An unidentified error has occurred, Please try again. If the problem continues, please contact your support team.
Environment:
1 site: Site1
2 Pools:
1. Lync 2010
Trusted application is added here for the site.
2. Lync 2013
Avaya phone system: AES r6-1-2-32-0
I have not moved the trusted application to the Lync 2013 pool yet, but my understanding is that it should still work since it’s in the site. Is my understanding on this correct? (All of my other trusted applications do work for Lync 2013
users & none of them have been moved yet. Remote Call Control is the only one that does not work.)
This is from the uccapi log. This is just from the user logging in, not actually making a call. Below are the items that I think are important, however, I don’t know how to interpret it to determine if the problem is on the Lync side or
the Avaya side. Here’s a summary:
SIP/2.0 100 Trying
Authentication-Info: TLS-DSK qop="auth", opaque="5FD217E1", srand="E05700E2", snum="9", rspauth="f308eae87c0bbe64a1ab213574776cbdf9823ab6", targetname="lync03.domain.com",
realm="SIP Communications Service", version=4
From: <sip:[email protected]>;tag=bbb282ebbd;epid=a86d5b0a29
To: <sip:[email protected]>
Call-ID: 9eb0d23a3b8f4e0eafc6c6da622fbecf
CSeq: 1 INVITE
Via: SIP/2.0/TLS 10.155.48.96:61472;ms-received-port=61472;ms-received-cid=1FA400
Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FUdcAgent
Content-Length: 0
SIP/2.0 200 OK
Authentication-Info: TLS-DSK qop="auth", opaque="5FD217E1", srand="15C0F9A2", snum="13", rspauth="4fd891e39a33e902fb1cec5d980e5bf0ccb172a0", targetname="lync03.domain.com",
realm="SIP Communications Service", version=4
From: <sip:[email protected]
>;tag=bbb282ebbd;epid=a86d5b0a29
To: <sip:[email protected]
>;tag=A7A45C856ECD79121A1827265ABBD7F6
Call-ID: 9eb0d23a3b8f4e0eafc6c6da622fbecf
CSeq: 1 CANCEL
Via: SIP/2.0/TLS 10.155.48.96:61472;ms-received-port=61472;ms-received-cid=1FA400
Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FUdcAgent
Content-Length: 0
SIP/2.0 487 Request terminated
Authentication-Info: TLS-DSK qop="auth", opaque="5FD217E1", srand="F46EC133", snum="14", rspauth="1d92718caa4f61d967faa46a5c256aafa8b4e740", targetname="lync03.domain.com",
realm="SIP Communications Service", version=4
From: <sip:[email protected]
>;tag=bbb282ebbd;epid=a86d5b0a29
To: <sip:[email protected]
>;tag=A7A45C856ECD79121A1827265ABBD7F6
Call-ID: 9eb0d23a3b8f4e0eafc6c6da622fbecf
CSeq: 1 INVITE
Via: SIP/2.0/TLS 10.155.48.96:61472;ms-received-port=61472;ms-received-cid=1FA400
ms-diagnostics: 5002;reason="Request was cancelled";AppUri="http%3A%2F%2Fwww.microsoft.com%2FLCS%2FUdcAgent";source="lync03.
domain.com"
Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FUdcAgent
Content-Length: 0Hi Suelizy,
To better understand the issue, I would like to collect the following information for troubleshooting:
1. Do you mean the Lync 2010 user can connect to the Phone System?
2. What’s next hop pool of the application?
In a mixed environment, you must set the next hop pool to be the Lync Server 2013 pool.
Best regards,
Eric -
Dear All,
I cannot connect to my Exchange account in Outlook 2013 using "Microsoft Exchange Server or Compatible Service".
First I would like to present my network environment, I have 4 physical servers;
The first one is holding the Domain Controller 1, IP@: 192.168.1.10
The second server is holding the additional Domain Controller which it is DC2, IP@: 192.168.1.11
The third server is holding the Exchange 2013 Mailbox, IP@: 192.168.1.15
And the last server is holding the Exchange 2013 CAS-HT, IP@: 192.168.1.16
I am doing the steps below:
1-Creating a new profile in outlook and start configuring the exchange account by entering the IP address of the Exchange-CAS Server, 192.168.1.16
2-entering the account name: [email protected]
3-Go to "More Settings" > "Connection" > "Connect to Microsoft Exchange using HTTP" > and entering the "Exchange Proxy Settings"
4-type the exchange CAS Server URL, https://192.168.1.16
5-Check the "Connect using SSL Only"
6-Authentication Settings: "NTLM Authentication", and pressing Apply
7-When I press the "Check Name" button, a message occurred> "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action".
8-I go back to the "Exchange Proxy Settings" and I Uncheck the "Connect using SSL Only" and pressing Apply
9-i press the "Check Name" Button, a small window occurred to enter a Username and Password, so I enter the Administrator username and the administrator password and pressing "OK", but nothing is changed, I tried to enter my
username and password in the small window and I still got the same result.
I cannot verify the account name and I cannot complete the process.
I appreciate you kind assistance.Hi,
To narrow down the cause, I’d like to recommend the following troubleshooting:
1. Try to login the test account through OWA.
2. Check the Autodiscover settings: get-clientaccessserver |fl autodiscoverserviceinternaluri
3. Check the result of directly accessing the following URL:
https://autodiscover.domain.com/autodiscover/autodiscover.xml
Thanks,
Angela
Angela Shi
TechNet Community Support -
Cannot Connect to Google Calendar in Mail, Contacts & Calendars preferences
I recently obtained a new Mac and am playing with Mountain Lion for the first time. I'm trying to add my Google Apps (custom domain, not @gmail.com) account to the Mail, Contacts & Calendars control panel. I was able to add Mail, Messages, and Notes without any issues, but it's refusing to connect to Calendars & Reminders. When I attempting connecting, it gives me an error...
A secure connection couldn't be established.
Click “Continue” to continue creating the account. You can edit the account later in Calendar preferences if necessary.
So I click "Continue" to... well, continue. Eventually, I've given this error:
There was a problem setting up the account.
Calendar couldn't discover the account settings for the CalDAV server “google.com”.
Just out of curiousity, I went into the Calendar app to directly add my Google account. Doing so also gives me an error:
Server with Secure Communication Unavailable
Your calendar account isn't on a server that can receive your calendar securely.
If a server isn't secure, others may be able to view your calendar information. To continue searching for your account on servers that may not be secure, and then set up the account if it's found, click Continue.
So I go ahead and click Continue. After waiting some more, I finally get the error...
No CalDAV servers were found for "google.com".
This message appears on the Account Settings sheet where you can add a CalDAV account. If I manually type in the Server Address here (https://www.google.com/calendar/dav/[email protected]/user//www.google.com/calendar/dav/[email protected]/user), Calendar claims it still cannot connect to a secure connection. This time, clicking Continue does add the account. (I'm assuming through a non-secure conncetion.) If I try to edit the Account Settings, it takes me to the Mail, Contacts, and Calendars control panel where Calendars & Reminders for my Google account is now selected.
I can only assume this is a weird bug with Mountain Lion, but needless to say, this is far from the "it just works" mentality I've been use to.
This was not an issue with iCal on Snow Leopard, which is what I'm coming from.I was having similar issues and thought I would put down what solved my problem.
In "Mail, Contacts & Calendars" I didn't choose "Gmail" I used "Add Oter Account…" as previously mentiond.
Then I chose "Add a CalDav account"
Under User Name: I entered my entire gmail address
Under Password: I entered a new "Application Password" key as generated by Googles two step verification process.
Under Server Address: I tried to use just "google.com" and "www.google.com" neither of these worked - only errors. So I used the address as listed on Google Calender when clicking on settings for my main calendar. There is a link that will give you your calendars private address. I shortened it to:
www.google.com/calendar/ical/your_gmail_address_goes_here
Then it worked immediately! -
I have a Windows 2012 Server set up offering print services to our network, there are about 20 printers set up all deployed via group policy. Recently, on one of our Windows 7 machines I am finding that I an unable to connect to one of the printers shared
on the print server while other clients seem to be able to connect to the same printer with no problem. Also, the printer used to work just fine from this same Windows 7 machine.
To test things further I logged onto the Win7 machine as the domain administrator, connected to the print server and double clicked on the printer to attempt to install it manually (rather than letting Group Policy do it). When I do so I receive the following
message, "Windows cannot connect to the printer. Operation failed with error 0x00004005.
I have done some searching but the only references I am finding to this particular error message involved users attempting to connect to a printer hosted on a 32-bit version of Windows from a 64-bit client. However, in my case both the server and client
are 64-bit.
Can any one help me troubleshoot this 0x00004005 error?
Thank you.Sorry for the delay. I just went and attempted to add the printer again on the client machine, the installation failed just as before, no log entries were recorded in the PrintService Admin log and the Operational log was disabled, I enabled it and added
the printer again. This time when the installation failed seven log entries appeared in the Operational log, all of them informational, no errors or warnings, the events are as follows...
1. Event 300, Printer {71688D29-F70C-42F2-90E1-DA5D450E772D} was created. No user action is required.
2. Event 304, Printer {71688D29-F70C-42F2-90E1-DA5D450E772D} was resumed. No user action is required.
3. Event 306, Settings for printer {71688D29-F70C-42F2-90E1-DA5D450E772D} were changed. No user action is required.
4. Event 306, Settings for printer {71688D29-F70C-42F2-90E1-DA5D450E772D} were changed. No user action is required.
5. Event 302, Printer {71688D29-F70C-42F2-90E1-DA5D450E772D} will be deleted. No user action is required.
6. Event 302, Printer {71688D29-F70C-42F2-90E1-DA5D450E772D},8 will be deleted. No user action is required.
7. Event 301, Printer {71688D29-F70C-42F2-90E1-DA5D450E772D} was deleted, and users will no longer be able to print to this printer. No user action is required.
There are a couple log entries in the Admin log indicating an error occurred, those errors occurred yesterday afternoon at 4:30pm or so. I did not try to add the printer then so I don't know if these are related to this particular problem or not. This same
entry appeared twice at exactly the same time...
The print spooler failed to load a plug-in module C:\Windows\system32\spool\DRIVERS\x64\3\PrintConfig.dll, error code 0xc1. See the event user data for context information.
As a temporary workaround I installed the drivers for that printer directly on the Windows 7 client machine and that works fine, however this is less than ideal because I had set up group policy to only install that printer for specific users, not for everyone.
Maybe you are looking for
-
Is it possible to scroll the lyrics of the same music? some lyrics are large, and is hard to see. It is possible to scroll the lyrics???? please help me!!!!!!
-
Unable to load DLL ELCOMProxies.dll while creating Enterprise Message Sourc
Hi All, I am getting following error when I try to create Enterprise Message Source of type "Oracle (AS JMS and OJMS)". Oracle.BAM.Common.Exceptions.CommonException: Unable to create Message Receiver Admin COM object: Error=System.DllNotFoundExceptio
-
My home email is RoadRunner which is not compatible with the iPhone at all .. tho there was a time when I could at least get my emails even tho I couldnt reply .. its a RoadRunner/ATT snafu over security. Then the incoming stopped and I decided I did
-
What is span equivalent in the content question
<h:panelGroup layout="span" ......I am searching for the equivalent in adf ...
-
Vanishing point – Marquee tool – problems with pasting images
For some reason when I paste my selected image into the Vanishing Point tool it comes in with a marquee that is exactly 4 times the size of the image that I originally selected and copied. This completely throws the perspective off as for some reason