Hi,

I have standalone root ca server 2008 Enterprise 32bit SP1 and SubCA Server 2008 R2 Standard 64bit SP2,

When I submit renew CA Certificate request (same key) from SubCA in my root ca I get an error parameter is incorrect,

The first and only request that was issued by root ca to SubCA  was in 2011, When I compare 2011 and 2019 renew ca requests I see only 1 difference - in 2011 SubCA  was SP1 and now its SP2 while root remains SP1,

Can this be the reason for the error as root CA SP1 cannot accept renew CA Certificate request from a server that runs SP2? 

Hello, 

I have been trying to install/update Security Monthly Quality Rollup for Windows 7 for x64-based Systems. But I cannot update. 

The last error code from Windows Update is 800F0818.  It has been updating Defender Antivirus no problems, but almost nothing else. 

Then I tried to run SYSTEMINFO.EXE to get list of hotfixes but it does not show any and it showed "N/A" only.  

I have tried to run System Update Readiness Tool for Windows 7 (KB947821) but it did not help. SFC.EXE did not any errors. 

Please help me what to do.  Thank you. 

Hi,

Any idea about tracking the consumption of keys, information about the machines upon activation is done?. i want to know how many PC has been activated from KMS

Thanks,

---

IT Helpdesk

System : Server 2012 Standerd, main system and AD.

Problem: "MMC can't open C:/Windows/System32/services.msc..."

First step:

The first error was due to a file being corrupted message. I escalated the user profile and took control of the file using admin cmd with takeown and icals, both taking full ownership and full access(what a struggle)

Second step:

When trying to launch it from the server management console it now gave me this error MMC.... you require permission from Administrator(the account I am logged in with). Launched an escalated MMC console with the same result(server management console as well) But when using the component management console it works fine. I tried replacing the file by creating a new services.msc, but is unable to save the file to the directory even after stopping all the services(you require permission from Administrator(the account I am logged in with)).

Thus the file is not corrupted any more but still can't be accessed using mmc or SMC.

Google it and forum search, with no luck.

Third and final step:

Panic like hell and open a forum chat

HELP please

PS: This all occurred after a power failure.When the machine was booted after the power failure, i received an fatal error on the raid web console about rejected cache on server starup

I have installed the Security Update for Microsoft Windows SMB Server (4013389) in a Windows Server 2003, when the server was about to restart, appeared a message informing that there was more updates to install. I clicked on yes in order to install the other updates, but after reboot, I was not able to log in the domain. I can only log in locally. I saw that the Workstation Service was not started and therefore all those services that depend on this. When I try to start it, it is displayed: 

"Could not start the Server service on Local Computer. Error 1075 the dependency service does not exist or has been marked for deletion. I have checked the registry and everything seems ok. Who has had this problem? What can I do?

Thanks

Alberto

Good morning, all!

Starting the move from my 2008 R2 AD controllers to a new pair of 2012 R2 servers. These are all virtual machines in a VMware stack. I looked closely at this blog and the process seems fairly straightforward.

However, I have two DCs, one in each of my two datacenters. The new configuration will have the same look, a DC in each DC. I want to make this as smooth as possible, so are there any concerns about what order to make the changes, or remove one 2008 controller to make the transition easier, or other issue to consider.

I also have a separate server providing AzureADConnect services. Any thoughts on coordinating this with the DC upgrades?

Thanks to all for looking!

Gregg

hello ;

i have windows server 2008 R2 running as a primary domain controller , with other domain controller (2008 R2)

the PDC stop running and it display this famous error when we start the VM (it run as a virtual machine )

STOP: c00002e2 Directory Services could not start because of the following error:
A device attached to the system is not functioning.
Error Status: 0xc0000001.

what I found on googling is that the ntds database is corrupted and I need to repair it

the solution I found talk about  rebooting the VM and enter the DSRM with F8

then delete the log files under c:\windows\NTDS\ and reboot ( i did this but nothing happen)

or try to repair the ntds.dit database using the esentutle cmd line :

this what I get when I tried it :

C:\Windows\system32>ntdsutil.exe
ntdsutil.exe: activate instance ntds
Active instance set to "ntds".
ntdsutil.exe: files
Could not initialize the Jet engine:  Jet Error -528.
Failed to open DIT for AD DS/LDS instance NTDS. Error -2147418113
ntdsutil.exe:

it show that there is an issue with the database , so i tried to repair it using the esentutl.exe cmdl

C:\Windows\System32>esentutl.exe /g C:\Windows\NTDS\ntds.dit

Extensible Storage Engine Utilities for Microsoft(R) Windows(R)
Version 6.1
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating INTEGRITY mode...
        Database: C:\Windows\NTDS\ntds.dit
  Temp. Database: TEMPINTEG10212.EDB

Checking database integrity.

                     Scanning Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |----|----|----|----|----|----|----|----|----|----|
          ...................................................

Integrity check completed.  Database is CORRUPTED!

Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database fi
le or corrupted db) after 2.855 seconds.



C:\Windows\System32>esentutl.exe /p C:\Windows\NTDS\ntds.dit

Extensible Storage Engine Utilities for Microsoft(R) Windows(R)
Version 6.1
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating REPAIR mode...
        Database: C:\Windows\NTDS\ntds.dit
  Temp. Database: TEMPREPAIR8540.EDB

Checking database integrity.

                     Scanning Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |----|----|----|----|----|----|----|----|----|----|
          ...................................................

Initiating DEFRAGMENTATION mode...
            Database: C:\Windows\NTDS\ntds.dit

                  Defragmentation Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |----|----|----|----|----|----|----|----|----|----|
          ....
Operation terminated with error -327 (JET_errBadPageLink, Database corrupted) af
ter 10.15 seconds.

C:\Windows\System32>

the operation failed since the integrity check failed 

event viewer gives the following error :

error id 1168 : 

The description for Event ID 1168 from source Microsoft-Windows-ActiveDirectory_DomainService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
31
1f
2021486

before running these steps i also got this error :

error id 1003

The description for Event ID 1003 from source Microsoft-Windows-ActiveDirectory_DomainService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

-530
JET_errBadLogSignature, Bad signature for a log file

any help will be appreciated , thank's

I performed an online BIOS update on HPE BL620c G7 from I25 05/23/2011 to I25 05/21/2018. The server running on Windows Server 2012 Datacenter. Three days later, the server reboots randomly with Event ID 1001 "The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x0000000000000028, 0x0000000000000002, 0x0000000000000000, 0xfffff880015364b2)" after BIOS Update

Windows 2016 DC freshly installed and following warnings logged by BPA. So do I want the default or the recommended by the BPA? If the recommend why is it not set to recommended by default?

Problem:
Smb2CreditsMin doesn't have the recommended value on this server.

Impact:
SMB not in a default configuration, which could lead to less than optimal behavior.

Resolution:
Set Smb2CreditsMin to the recommended value, 128.

BPA model version: 1.0
----------------------
Problem:
DurableHandleV2TimeoutInSeconds doesn't have the recommended value on this server.

Impact:
SMB not in a default configuration, which could lead to less than optimal behavior.

Resolution:
Set DurableHandleV2TimeoutInSeconds to the recommended value, 30.
----------------------
Problem:
CachedOpenLimit doesn't have the recommended value on this server.

Impact:
SMB not in a default configuration, which could lead to less than optimal behavior.

Resolution:
Set CachedOpenLimit to the recommended value, 5.

---------------------------
Problem:
Srv.sys is not set to start on demand.

Impact:
Client computers will not be able to access file shares and other Server Message Block (SMB)-based network services on this computer.

Resolution:
Set Srv.sys to start on demand.

------------------------------
Problem:
In addition to the normal file names, the server is creating short, eight-character file names with a three-character file extension (8.3 file names) for all files.

Impact:
Creating short file names in addition to the normal, long file names can significantly decrease file server performance.

Resolution:
Disable short file name creation unless short file names are required by legacy applications.

------------------------------
Problem:
AsynchronousCredits doesn't have the recommended value on this server.

Impact:
SMB not in a default configuration, which could lead to less than optimal behavior.

Resolution:
Set AsynchronousCredits to the recommended value, 64.

------------------------------
Problem:
AutoDisconnectTimeout doesn't have the recommended value on this server.

Impact:
SMB not in a default configuration, which could lead to less than optimal behavior.

Resolution:
Set AutoDisconnectTimeout to the recommended value, 0.

--------------------------------
Problem:
Smb2CreditsMax doesn't have the recommended value on this server.

Impact:
SMB not in a default configuration, which could lead to less than optimal behavior.

Resolution:
Set Smb2CreditsMax to the recommended value, 2048.

hello, in my environment:

all the domain joined computer will sync time from DC, that's fine!

all the DC (except PDC ) will sync time from PDC, that's fine too!

but I wanna PDC can auto sync time from external NTP , such as time.windows.com

I tried below command on PDC, but it seems like "one time sync" only.

W32tm /config /manualpeerlist:time.windows.com,0x1 /syncfromflags:manual /reliable:yes /update
net start w32time & W32tm /resync /rediscover

after the command ran, the time is correct, but if I modify time on PDC, the time seems not able to auto correct from external NTP.

I recently found that once we disable Negotiate Authentication on WinRM Service on Domain COntrollers, the WinRM Clients cannot Authenticate with those Target Servers using WAC. 
I am trying to find if anyone has seen this issue or behaviour.

Windows Admin Center(WinRM Client)
Windows 2012 or Windows 2016 Domain Controllers(WinRM Servers)

When I disable the Negotiate Authentication using Group Policy or using Winrm locally, WinRM Client fails to Authenticate when I test the connection from Windows Admin Center.
Also, the poweshell CMDLets i:e Enter-Pssession or Invoke will fail with the same error unless I specify the -Authentication Switch and force the usage of Kerberos

I tried disabling Negotiate Authentication on WinRM Client setting however that doesn't help. ALso trusted Host is updated for all Target Host.

Error message.

"Connecting to remove server Servername failed with the following error message: The WinRM client cannot process the request. Negotiate authentication is currently disabled in the client configuration. Change the client configuration, use one of the enabled authentication mechanisms still enabled. To use kerberos, specify the local computer name as the remote destination."


Question with the two scenarios:-
Winrm Client has Negotiate and Kerberos Enabled
WinRM Service has Negotiate Disabled and Kerberos Enabled
Why is the WinRM Client not failing over to Kerberos when Negotiate fails? Is fail over an expected behavior?

WinRM Client and WinRM Service has Negotiate Disabled 
WinRM Client and WinRM Service has Kerberos Enabled
Why is the WinRM cilent not using Kerberos when I it is enabled on both the sides and still uses Negotiate Authentication.

Hi,

I'm having random Blue Screen BSOD Stop crashes on an HPE Proliant ML110 Gen9 running Windows Server 2012 R2. Event reads "operating system failure windows bug check stop 0x00000133".

Hardware diagnostics with HPE Insight Diagnostics show no error. Updated to latest firmware and drivers with HPE Service Pack for Proliant.

There's this HPE KB article https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c03617930

It points to this Microsoft KB article which includes a hotfix https://support.microsoft.com/en-us/help/2789962/you-receive-a-dpc-watchdog-violation-133-stop-error-message-on-a-windo

However, attempting to download the hotfix gives a "Hotfix not available" message.

There's an identical HPE Proliant ML110 Gen9 server with same software installation which is not experiencing these crashes, so I'm not sure yet if it's a hardware issue.

Could anyone please provide with information regarding this hotfix? Any more recent hotfix that supersedes this one?

Thanks

When i run the command 

Dism /online /set-edition:serverstandard /accepteula /productkey:<>   it says Setting an edition is not supported with online images but when I run dism /get-targeteditions I can go to serverstandard

This is what I get in DISM log file

2019-09-16 09:51:15, Info                  DISM   PID=6120 Scratch directory set to 'C:\Users\ADMINI~1\AppData\Local\Temp\1\'. - CDISMManager::put_ScratchDir
2019-09-16 09:51:15, Info                  DISM   PID=6120 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadImageSession
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:15, Info                  DISM   DISM Manager: PID=6120 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:15, Info                  DISM   DISM.EXE: 
2019-09-16 09:51:15, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2019-09-16 09:51:15, Info                  DISM   DISM.EXE: 
2019-09-16 09:51:15, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=3
2019-09-16 09:51:15, Info                  DISM   DISM.EXE: Executing command line: "C:\Windows\system32\Dism.exe"  /online /Set-Edition:ServerStandard /ProductKey:TMJ3Y-NTRTM-FJYXT-T22BY-CWG3J /AcceptEul
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2019-09-16 09:51:15, Info                  DISM   DISM Provider Store: PID=6120 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Manager: PID=6120 Successfully loaded the ImageSession at "C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113" - CDISMManager::LoadImageSession
2019-09-16 09:51:16, Info                  DISM   DISM Image Session: PID=4032 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  DISM   DISM OS Provider: PID=4032 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2019-09-16 09:51:16, Info                  DISM   DISM OS Provider: PID=4032 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Getting Provider OSServices - CDISMProviderStore::GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Warning               DISM   DISM Provider Store: PID=4032 Failed to Load the provider: C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Manager: PID=6120 Image session successfully loaded from the temporary location: C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113 - CDISMManager::CreateImageSession
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Getting Provider OSServices - CDISMProviderStore::GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.24516_none_6810bdd8f70626d9\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2019-09-16 09:51:16, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.24516_none_6810bdd8f70626d9\pkgmgr.exe" : got STATUS_SUCCESS
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Target image information: OS Version=6.1.7601.24516, Image architecture=amd64
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.24516_none_6810bdd8f70626d9\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2019-09-16 09:51:16, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.24516_none_6810bdd8f70626d9\pkgmgr.exe" : got STATUS_SUCCESS
2019-09-16 09:51:16, Info                  DISM   DISM Package Manager: PID=4032 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2019-09-16 09:51:16, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.24516_none_6810bdd8f70626d9\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2019-09-16 09:51:16, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.24516_none_6810bdd8f70626d9\pkgmgr.exe" : got STATUS_SUCCESS
2019-09-16 09:51:16, Info                  DISM   DISM Package Manager: PID=4032 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2019-09-16 09:51:16, Info                  DISM   DISM Package Manager: PID=4032 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.24516_none_6810bdd8f70626d9\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2019-09-16 09:51:16, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.24516_none_6810bdd8f70626d9\pkgmgr.exe" : got STATUS_SUCCESS
2019-09-16 09:51:16, Info                  DISM   DISM OS Provider: PID=4032 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2019-09-16 09:51:16, Info                  DISM   DISM Driver Manager: PID=4032 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\1\22FCF93A-78B9-4CA0-9DFB-1393D7549113\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2019-09-16 09:51:16, Info                  DISM   DISM Transmog Provider: PID=4032 Current image session is [ONLINE] - CTransmogManager::GetMode
2019-09-16 09:51:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Getting Provider Edition Manager - CDISMProviderStore::GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2019-09-16 09:51:16, Info                  DISM   DISM Transmog Provider: PID=4032 Current image session is [ONLINE] - CTransmogManager::GetMode
2019-09-16 09:51:16, Info                  DISM   DISM Transmog Provider: PID=4032 Current image session is [ONLINE] - CTransmogManager::GetMode
2019-09-16 09:51:16, Info                  DISM   DISM Transmog Provider: PID=4032 GetProductType: ProductType = [LanmanNT] - CTransmogManager::GetProductType
2019-09-16 09:51:16, Error                 DISM   DISM Transmog Provider: PID=4032 Setting an Edition is not supported online. - CTransmogManager::ExecuteCmdLine
2019-09-16 09:51:16, Error                 DISM   DISM Transmog Provider: PID=4032 [Upgrading system]: Setting an Edition is not supported with online images.
 [hrError=0x80070032] - CTransmogManager::EventError
2019-09-16 09:51:16, Info                  DISM   DISM Image Session: PID=4032 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Package Manager: PID=4032 Finalizing CBS core. - CDISMPackageManager::Finalize
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:16, Info                  DISM   DISM Provider Store: PID=4032 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:17, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2019-09-16 09:51:17, Info                  DISM   DISM.EXE: 
2019-09-16 09:51:17, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2019-09-16 09:51:17, Info                  DISM   DISM.EXE: 
2019-09-16 09:51:17, Info                  DISM   DISM Image Session: PID=6120 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2019-09-16 09:51:17, Info                  DISM   DISM Provider Store: PID=6120 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2019-09-16 09:51:17, Info                  DISM   DISM Provider Store: PID=6120 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2019-09-16 09:51:17, Info                  DISM   DISM Provider Store: PID=6120 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

Hi, if I configure my server to get time from the NTP pool using this command:

w32tm /config /syncfromflags:manual /manualpeerlist:"0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org"

...will the server re-query DNS to get a new IP from the NTP pool if one of the current servers stops responding?

Thanks

We are using RAS to facilitate connections for our remote Windows NVRs so we don't have to open ports to public. The software is Geovision and has its own Web Server and authentication system. We do not use remote desktop from the remote video recorders and use L2TP VPN always on connections. From my understanding we do not need CALs to authenticate with server either through local user manager or even AD user.

We have CALs for our road warriors and others that RDP back in through the same VPN and are running out of CALs. To be compliant I want to confirm we in fact need device CALs for these video recorders using the RAS server or do I need to move to OpenVPN or other Open Source VPN sources since these are just unmanned devices.

After the latest update I am now getting a popup message from Network Connections that says

"An error occurred while reconnecting M: to \\mybookworld\Public\Customer Files

Microsoft Windows Network: The local device is already in use.

This connection has not been restored."

How do I stop this?

 

sir my name is mahesh i tried un install apche  tomcat 8 and 9 .these are un install os but it will be show on servises. how to delete apche tomcat in services

Running Windows server 2016, I have a JBOD directly attached to this server, in the File and  Storage services under Disks it is showing that I have 33 disks, 1 for the windows drive, and then the JBOD has 16 physical disks installed. Why then is the file and storage services showing that i have 33 disks when it should show 17. Have added pics below on how I have it connected right now, do not have to much experience with JBODs. But then also when i look under storage pools it only shows that I have 8 physical disks. Lastly, when I goto the "new volume wizard" it only shows the 16 physical drives that are installed. Im so retardadly confused right now.

One other thing, I am trying to figure out how to do a RAID on the JBOD disks, is that possible? I can find almost no documentation on if i can do that or if im just chasing a pipe dream.

Server is a Dell R900

   Any advice is VERY much appreciated.

File and Storage Services Disks View

Storage Pools Physical Disk View

New Volume Wizard screen

Please on my Active directory i deployed single sign on for all users but discovered it not really working so i decided to reconfigure it.while deploying there is section where i was asked to input domain administrator credential which i did but got an error that "an error occur while locating the computer account" mean while the username and password is correct.Kindly assist to rectify it.Thanks

Hi All,

We have deployed some new 2019 domain controllers are are having issues where LDAP queries are coming back with:

00000008: SysErr: DSID-0205199E, problem 12 (Not enough space), data 0

Turning on diagnostic NTDS logging the domain controller logs (Event ID: 1535):

Internal event: Active Directory Domain Services has encountered the following exception and associated parameters. 

Exception:
e0010003 
Parameter:
0 

Additional Data 
Error value:
0 
Internal ID:
205199e

Internal event: The LDAP server returned an error. 
 
Additional Data 
Error value:
00000008: SysErr: DSID-0205199E, problem 12 (Not enough space), data 0

The domain controller has plenty of space 80Gb. The issue seems to occur when LDAP clients use the filter syntax: memberOf:1.2.840.113556.1.4.1941:

Has anyone seen this error before?.  Dcdiag and repladmin are clean.