I have version 1904 of Windows Admin Center installed on my Server 2019 server. Windows Admin Center has been installed on this server for about 10 months and now it seems the certificate for Windows Admin Center is expired.
How can I get a new certificate that is not expired for Windows Admin Center? If I install the newest version of Windows Admin Center (version 1910) then will this give me a new unexpired certificate?
Hello,
I received an alert from by Netwrix appliance that inform me that:
Who: | NT AUTHORITY\ANONYMOUS LOGON |
Action: | Modified |
Object type: | user |
What: | \local\Domain-name\Users\DOMAININFO$ |
When: | 01/11/2019 17:55:17 |
Where: | DCServer.Domain-name.local |
Data source: | Active Directory |
Monitoring plan: | Monitoring plan AD |
Item: | Domain-name.local (Domain) |
RID: | 2019110117-blablablaxxxxx |
Could you help me to analyze this event ?
Thanks
Remote Desktop cannot verify the identity of the computer you want to connect to. This problem can occur if:
Contact your network administrator or the owner of the remote computer for assistance.
After installing the Windows October patches (KB4519972, KB4519561, KB4515854, kb4516655) on several of our 2008 R2 servers, any IIS application pools that were running from a Local or Domain account would not start. The windows event error was Event ID:
5059 "Application pool --- has been disabled. Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool". When restarting the pool it just gives another WAS error. Also received
the pictured error which prompted me to look at Log on as batch rights.
I tried uninstalling all the updates, as well as trying to roll back from .Net 4.7.2 to 4.5, and even did a full VM restore to before the updates and still the App pools will not start. I compared every single group policy (before & after) and they are
identical. The account is part of local administrators, IIS_IUSRS, and has locally applied log on as batch rights. I could not find any recent changes to user accounts, The username/password definitely were not changed. We have AV installed but ran a full
scan from another AV and returned clean. The resolve to get the App pools back up and running was to create a service account that had "Log on as batch rights" applied from the domain gpo.
Fast forward a week and we had another servers app pools go down with the same errors after a server reboot. However, this server hadn't been patched in 2 months and no changes had been made. The reboot made me think policy again so did a backup from 2 weeks
prior and brought it up completely disconnected from the network. App pools down again. As far as I could tell the server was identical. If you notice in the screen shot that it's just displaying the SID - unfortunately since this was a backup from restore
of the production server I can't confirm whether it's simply because it's a domain acct and this server is running completely offline, OR maybe the issue of displaying the SID and not being able to resolve the actual user name could be the root cause? The
fix was the same. I added that service account to the Log on as Batch policy and it starts again.
So here I am after days of troubleshooting, I have a "fix" (forcing batch logon rights through domain policy), but after searching all the tech forums I still have no idea what the root cause is. If the SID issue could be the cause, then what would
cause THAT to happen, and to 8 different servers over the course of a week?? The commonalities are Win Server 2008, IIS 7, and that the server was rebooted. Nothing else changed that I'm aware of. Please help!
We are having issues with Roaming profiles on Windows 10 computers. We are currently running an existing SBS2011 server with four Windows 7 workstations All users (4 total) use roaming profiles. Added new 2016 server as a DC and adding four new Windows 10 desktops to replace the Windows 7 systems.
Two existing Roaming profiles (profile A and B)are able to login to the Windows 10 computers (Computers 1 and 2) without any issues. Two of the other existing Roaming profiles (profile C and D) are having issues logging into the new Windows 10 computers (Computers 3 and 4).
Profile C will not login to any of the new Windows 10 computers and receives the following error on all of the Windows 10 computers. “We can’t sign in to your account. This problem can often be fixed by signing out of your account and then signing back in. If you don’t sign out now, any files you create or changes you make will be lost.”
Profile D will correctly login to one of the new Windows 10 computers (Computer 3) but, receives the following error when trying to login to the same computer as Profile C . “We can’t sign in to your account. This problem can often be fixed by signing out of your account and then signing back in. If you don’t sign out now, any files you create or changes you make will be lost.”
Any thoughts on what may be causing the issue? Thanks!
Jack - IT Portfolio
We have a server running Windows Server 2016 Essentials with Windows Server Backup backing up to a WD My Passport external hard drive. Over the past year, we've seen random warnings where backups were "Completed with warnings" and the bare metal restore portion failed. These warnings happen inconsistently from once a month to several times a month (6 times last month). We don't see any patterns that cause it to fail or succeed. There aren't any other scheduled tasks or backups running during this time.
The eventlog has several errors at the backup time:
1. Source: DeviceSetupManager Event ID: 131 - Metadata staging failed, result=0x8007000D for container '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
2. Source: VSS Event ID: 8229 -
A VSS writer has rejected an event with error 0x800423f2, The writer's timeout expired between the Freeze and Thaw events.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
Thaw Event
Context:
Execution Context: Writer
Writer Class Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Name: Registry Writer
Writer Instance ID: {f2595c5a-ccdf-4122-aa1e-d7fff661237e}
Command Line: C:\Windows\system32\vssvc.exe
Process ID: 77643. Many Source: SPP errors Event ID: 16389
Writer System Writer experienced retryable error during shadow copy creation. Retrying... More info: . Writer ASR Writer experienced retryable error during shadow copy creation. Retrying... More info: . Writer Shadow Copy Optimization Writer experienced retryable error during shadow copy creation. Retrying... More info: . Writer FRS Writer experienced retryable error during shadow copy creation. Retrying... More info: . Writer Registry Writer experienced retryable error during shadow copy creation. Retrying... More info: . Writer COM+ REGDB Writer experienced retryable error during shadow copy creation. Retrying... More info: . Writer MSSearch Service Writer experienced retryable error during shadow copy creation. Retrying... More info: . Writer Windows Server Storage VSS Writer experienced retryable error during shadow copy creation. Retrying... More info: . Writer WMI Writer experienced retryable error during shadow copy creation. Retrying... More info: . Writer Certificate Authority experienced retryable error during shadow copy creation. Retrying... More info: . Writer NTDS experienced retryable error during shadow copy creation. Retrying... More info: . Writer IIS Config Writer experienced retryable error during shadow copy creation. Retrying... More info: . Writer Dhcp Jet Writer experienced retryable error during shadow copy creation. Retrying... More info: . Writer IIS Metabase Writer experienced retryable error during shadow copy creation. Retrying... More info: .
4. Source: Disk Event ID: 51 - An error was detected on device \Device\Harddisk2\DR133 during a paging operation.
5. Many Source: FilterManager Event ID: 3 - Filter Manager failed to attach to volume '\Device\Harddisk2\DR134'. This volume will be unavailable for filtering until a reboot. The final status was 0xC03A001C.
We tried the following without success:
Any help would be appreciated, thanks.
Log Name: Setup
Source: Microsoft-Windows-WUSA
Date: 11/14/2019 8:31:53 AM
Event ID: 3
Task Category: None
Level: Error
Keywords:
Description:
Windows update could not be installed because of error 2149842967 "" (Command line: ""C:\Windows\system32\wusa.exe" "C:\2019-05 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4494440)\AMD64-all-windows10.0-kb4494440-x64_390f926659a23a56cc9cbb331e5940e132ad257d.msu"")
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WUSA" Guid="{09608C12-C1DA-4104-A6FE-B959CF57560A}" />
<EventID>3</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-11-14T00:31:53.190657100Z" />
<EventRecordID>815</EventRecordID>
<Correlation />
<Execution ProcessID="6212" ThreadID="6196" />
<Channel>Setup</Channel>
<Computer></Computer>
<Security UserID="S-1-5-21-2397441296-3334134172-39446326-500" />
</System>
<EventData>
<Data Name="UpdateTitle">
</Data>
<Data Name="ErrorCode">2149842967</Data>
<Data Name="ErrorString">
</Data>
<Data Name="CommandLine">"C:\Windows\system32\wusa.exe" "C:\2019-05 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4494440)\AMD64-all-windows10.0-kb4494440-x64_390f926659a23a56cc9cbb331e5940e132ad257d.msu"</Data>
</EventData>
</Event>
Above is the detail, who can give me a suggestion or help? thank you in advance.
Kenneth
One of the Cluster group is returning a DNS bad key. It only happens when it is failing over to the primary node. There's no entry in the DNS for the Cluster group name. Have deleted the DNS entry and computer object for the cluster group and have done repairs but the error still exists. What could be the problem with the DNS?
Hi Experts,
Could you please share any scripts to find the memory slot and installed memory on each slot of servers.
I have used wmic MEMORYCHIP get command, but it is not giving any slot information.
Nidhin.CK System Analyst
We are running two virtual instance on AWS of microsoft windows server 2016 DC with 4vCore in each instance.
MSSQL server 2016 trial version installed in each instance.
Three DBs are configured in primary server.
Created one always on availability group for DB1, one read replica, sync replication, backup on primary replica.
Created second always on availability group for DB2, one read replica, sync replication, backup on primary replica.
Please let me know optimal required license details for the same.
Thanks & Regards Ishan Dhawan
Hi
please provide the downloadlink for MSDT need to troubleshoot the server related problems.
Hi Experts,
We are having five different offices in multiple cities and have total six DCs.
The computers at the HQ are updating group policies from remote DCs not from local and on the other note their logon server is local DC not the remote.
I have set all the sites with appropriate IP ranges in Sites and Services.
I am not getting why PCs are updating GPs from remote location not from local server?
Thank You.
Hi All,
Today while doing pre-checks before migration on AWS cloud server found that we are not able to create domain\username logins in SQL Instance hosted on it. however same was possible previously as we have existing logins there, verified in other 2 servers of same cluster servers. We found no issues there also tried to create forest domain\usernames logins in all the 3 servers and found no issue.
As shown below it resolves only SID value. Could you please any expert can help here to fix the issue. What can be the cause.?
Some related MS article found here https://support.microsoft.com/en-us/help/324321/how-to-troubleshoot-error-15401 but no resolution yet.
NLTest /dclist forboth return expected results from the correct regional DCs.
I'm also able to do things like get-aduser against both Prod and PC without specifying credentials.And, I can look up my PC user by SID as well (simulating a SID to name resolution):
We looked at this for a few hours and think it's related to the overall issue with Singapore DCs being in old Macro accounts vs proper core accounts.
our troubleshooting shows that this issue is intermittent and difficult to predict. This might explain why we were able to add trusted domain accounts in the past without issue,
CHANDU
Hello,
i have a server kms where i activate the office 2016. now i would like to know how to know the number of post who have their offices 2016 activated. running the slmgr.vbs / dlv command
gives me a phony number, see screenshot
Rayo_Muchacho
I need to be able to activate Windows Server 2019 but getting error.
cscript slmgr.vbs /ipk 12345-12345-12345-12345-V4QMY
Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid
The key is downloaded from VLSC for our organization.
I have a KMS host on Windows Server 2012 R2 with July 2016 Quality Roll Up KB3172614 and Servicing Stack KB3173424 installed. We do not use Active Directory for activation. So,according to this <doc> I have the prerequisites for this Windows Server 2012 R2 to be able to activate Windows Server 2019. And according to this <doc> the prerequisites as well. Currently we are activating Windows Server 2016 from this KMS host. Please tell me how I can troubleshoot and fix this problem.
Here is the same error in the Application event log:
Log Name: Application Source: Microsoft-Windows-Security-SPP Date: 11/6/2019 2:37:40 PM Event ID: 1017 Task Category: None Level: Error Keywords: Classic User: N/A Computer: corp-dc02.corp.xxx.com Description: Installation of the Proof of Purchase failed. 0xC004F050 Partial Pkey=V4QMY ACID=? Detailed Error[?]
P.S. What is going on with the microscopic font size in this TechNet forum?!
Hi,
Does anyone know where to get the above hotfix from? Microsoft are saying it's no longer available and that I should come here to ask the proper techies what to do :-)
Any help you can provide will be greatly appreciated.
I was going to paste some links to microsofts own website, but i'm not allowed to.
Best Regards
David Wilson
My .exe file is located in C:\users\me\desktop
When run it creates file.txt in c:\users\me\desktop.
When run from Task Scheduler it runs but does not create the file.txt.
Run whether user is logged on or not is checked
Run with highest privileges is not checked (if it is checked program does not run).
Configured for Windows Server 2008 R2
Hope someone can solve this issue.
Stephen
This issue is the reverse of the normal scenario, where you can open a local PSSession, but you can't connect remotely. In this instance, connecting remotely is fine, but a local PSSession fails.
Also, the computer cannot connect a client PSSession to remote (working) hosts. The remote host returns "Access Denied". Errors 161 and 142 (WSMan operation CreateShell failed, error code 2150859046) on the remote host WinRM event log. This is
because the host is trying to return an auth token to the client, which is not accepted.
Hopefully this will help other people to avoid spending literally hours on something that is trivial.
Symptoms
On the affected machine, trying to enter a PSSession to itself has the following results
New-PSSession $hostname ## FAILS New-PSSession $FQDN ## FAILS New-PSSession localhost ## SUCCESS
On a remote machine, a new PSSession to the affected machine using the hostname, FQDN and IP are all fine.
Running Test-WSMan shows the following results:
test-wsman -computername badcomputer test-wsman -computername badcomputer.example.net test-wsman -computername 10.230.0.13 test-wsman : <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859046" Machine="badcomputer.example.net"><f:Message>WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. </f:Message></f:WSManFault>
Running the above tests on a remote machine shows the expected results
Test-wsman -computername badcomputer.example.net wsmid : http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd ProtocolVersion : http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd ProductVendor : Microsoft Corporation ProductVersion : OS: 0.0.0 SP: 0.0 Stack: 3.
Environment
C:>netstat -ano | find "5985" TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING 4 TCP [::]:5985 [::]:0 LISTENING 4