Hello,

I would like to report a huge bug in Windows Server 2012 and 2016. For 2012 I need to try multiple times to log in to system using RDP but for upgrading 2012 to 2016 I can't log in at all. Everything is described here:

https://social.technet.microsoft.com/Forums/systemcenter/en-US/b45761b1-3949-4c9c-9e88-7d70cef6990f/long-delay-to-log-in-please-wait-for-the-local-session-manager?forum=ws2016

Basically during RDP logging in process lsass.exe process is parsing ALL local users which takes too much time and incoming RDP session is being disconnected. As far as I can see in Windows Event log about 800-900 local users are being parsed before disconnection occurs.

During logging in process lsass.exe is using large amount of CPU but this is probably realted to checking registry:

https://social.msdn.microsoft.com/Forums/getfile/1079226

As you can see in ProcessManager from time when RDP connection was made 21% of ALL Windows events logged in Process Manager was from lsass.exe process.

There is a easy way to replicate this issue:

I can replicate this bug
1) RDP to a newly created Windows Server
2) create a batch file with the following content:
:start
net user /add user%random%_%random% /random
timeout 1
goto start
open command prompt and execute the batch file.
Wait 20 minutes
try to RDP or connect via console. It won't work.

(and as far as I know it was replicated on MS side but for now nothing is being done or decided what to do with this problem).

Solution for this issue can be just extending RDP timeout which will work just fine because lsass.exe is using more CPU only during local users traversing and after logging in it just drops.

Any ideas/suggestions? Except "just use AD" ok? This specific scenario is on system which holds shared hosting accounts and local users are being used just for keeping website separated from each other and I really don't need AD for this one.

Thanks

When using the startmenu in fullscreen mode, the start menu won't open anymore after a restart. When you disable and re-enable fullscreen mode, it works once again until the next restart.

It seems to be the ShellExperienceHost:

Name der fehlerhaften Anwendung: ShellExperienceHost.exe, Version: 10.0.14393.447, Zeitstempel: 0x5819bf85
Name des fehlerhaften Moduls: StartUI.dll, Version: 10.0.14393.447, Zeitstempel: 0x5819be04
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000b96b0
ID des fehlerhaften Prozesses: 0xa50
Startzeit der fehlerhaften Anwendung: 0x01d2ecced8231441
Pfad der fehlerhaften Anwendung: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Pfad des fehlerhaften Moduls: C:\Windows\ShellExperiences\StartUI.dll
Berichtskennung: 563781c7-6fab-49ae-b3de-e0dd30c1c08c
Vollständiger Name des fehlerhaften Pakets: Microsoft.Windows.ShellExperienceHost_10.0.14393.447_neutral_neutral_cw5n1h2txyewy
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

It's also possible that this happens only to local admins.

Derived from this thread:
https://social.technet.microsoft.com/Forums/windows/en-US/5703e7b0-433a-4347-a572-a6da7938f35d/startmenu-wont-open-if-fullscreen-is-enabled?forum=ws2016

Configure Azure Backup fail on Windows Server 2016 Essentials (Japanese) Dashboard.
It seems like "SetMachinePassphrase request failed".

Log is below.

[9248] 170611.195806.8596: General: Initializing...C:\Windows\System32\Essentials\OnlineBackupGettingStartedWizard.exe
[9248] 170611.195806.9064: OnlineBackupObjectModel: OnlineBackupBacked created successfully.
[9248] 170611.195807.0002: OnlineBackupObjectModel: Async connect called
[9248] 170611.195807.0939: PfBinding: Information: [0] : Adding service dns identity [WS2016E] in proxy endpoint.
[9248] 170611.195807.1564: OnlineBackupObjectModel: OnlineBackup connector created
[9248] 170611.195807.1564: OnlineBackupObjectModel: Set connection identifier to 1
[9248] 170611.195807.1721: StorageOM: StorageBacked created successfully.
[9248] 170611.195807.1721: StorageOM: Set connection identifier to 1
[7068] 170611.195810.2978: StorageOM: Getting storage data from server
[10112] 170611.195834.6420: OnlineBackupObjectModel: Start Online Backup service
[10112] 170611.195839.5951: MailServiceUtils: Try to Refresh Tab, Id = 9e2df491-e5f2-4147-8be8-9bc1a5552d5f
[4876] 170611.195840.8451: OnlineBackupObjectModel: Connection created with provider
[4876] 170611.195840.8451: OnlineBackupObjectModel: Getting onlineBackup data from server
[5648] 170611.195840.8764: OnlineBackupObjectModel: OnlineBackup file spec information retreived from provider.
[5648] 170611.195840.8920: OnlineBackupObjectModel: OnlineBackup backup job information retreived from provider.
[5648] 170611.195840.9076: OnlineBackupObjectModel: OnlineBackup configuration retreived from provider.
[5648] 170611.195840.9076: OnlineBackupObjectModel: OnlineBackup configuration retreived from provider.
[5648] 170611.195840.9233: OnlineBackupObjectModel: OnlineBackup configuration retreived from provider.
[5648] 170611.195840.9233: OnlineBackupObjectModel: Online backup data retrieved from provider. Setting connected property to true.
[7068] 170611.195841.1733: CloudServiceEnvironment: Failed to download cloud service environment file.
[10112] 170611.195904.4038: OnlineBackupUI: Successfully generate the certificate. Thumbprint: 4AB3DDC1A02EEF5C3D77B4A49F7271B9C224B326
[10112] 170611.195906.1506: OnlineBackupObjectModel: GetOnlineBackupResources starting.
[10112] 170611.195906.1506: OnlineBackupObjectModel: Executing request: <GetOnlineBackupResources>b__0
[6824] 170611.195906.6819: OnlineBackupObjectModel: List of Azure resource has 1 entries
[6824] 170611.195906.6819: OnlineBackupObjectModel: Microsoft.WindowsServerSolutions.DataProtection.OnlineBackup.OnlineBackupResourceRequest completed by backend with error code: 0x0
[10112] 170611.195906.6819: OnlineBackupObjectModel: Synchronous GetOnlineBackupResources request succeeded.
[10112] 170611.195906.6819: OnlineBackupObjectModel: RegisterOnlineBackupRequest starting.
[10112] 170611.195906.6819: OnlineBackupObjectModel: Executing request: <RegisterOnlineBackup>b__0
[6824] 170611.195936.2280: OnlineBackupObjectModel: OnlineBackup configuration retreived from provider.
[6824] 170611.195937.9669: OnlineBackupObjectModel: OnlineBackup configuration retreived from provider.
[6824] 170611.195938.0295: OnlineBackupObjectModel: Microsoft.WindowsServerSolutions.DataProtection.OnlineBackup.RegisterOnlineBackupRequest completed by backend with error code: 0x0
[10112] 170611.195938.0607: OnlineBackupObjectModel: Synchronous RegisterOnlineBackup request succeeded.
[10112] 170611.195938.0763: OnlineBackupObjectModel: SetMachinePassphraseRequest starting.
[10112] 170611.195938.0763: OnlineBackupObjectModel: Executing request: <SetMachinePassphrase>b__0
[9676] 170611.195939.1545: OnlineBackupObjectModel: Connection lost with the onlineBackup provider
[9676] 170611.195939.1545: OnlineBackupObjectModel: Microsoft.WindowsServerSolutions.DataProtection.OnlineBackup.SetMachinePassphraseRequest completed by backend with error code: 0x80040258
[9676] 170611.195939.1545: OnlineBackupObjectModel: Set connection identifier to 5 on reconnection
[9676] 170611.195939.1545: OnlineBackupObjectModel: Reconnecting with onlineBackup provider
[10112] 170611.195939.1545: OnlineBackupObjectModel: Synchronous SetMachinePassphrase request failed.
[10112] 170611.195939.1545: Exception:
---------------------------------------
An exception of type 'Type: Microsoft.WindowsServerSolutions.DataProtection.OnlineBackup.OnlineBackupObjectModelException, OnlineBackupObjectModel, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' has occurred.
Timestamp: 06/11/2017 19:59:39
Message: 種類 'Microsoft.WindowsServerSolutions.DataProtection.OnlineBackup.OnlineBackupObjectModelException' の例外がスローされました。 (ErrorCode 0x80040258)
Stack: 場所 Microsoft.WindowsServerSolutions.DataProtection.OnlineBackup.SetMachinePassphraseRequest.SetMachinePassphrase()
場所 Microsoft.WindowsServerSolutions.DataProtection.OnlineBackup.UI.RegisterProgressPagePresenter.<OnActivate>b__2_0(Object state)

[9248] 170611.195939.1857: OnlineBackupUI: An error occurred during the execution of the wizard. Error message =

This improvement suggestion is based on a problem which occurred often to me in my professional career, which cost a lot of nerves.
The improvement would be to set up a workflow in a graphical representation, which contains all concerned persons at each step of the workflow. So to speak it would be a kind of extension to the task manager in Microsoft outlook, which not only shows what task are done or not done, but also at which point of the workflow the task is stuck, and which tasks are in the pipline.
For example:
I want to order a sample valve for a chemical plant. This order needs many approvals and work steps form the purchasing department and the material management. In present times many e-mail were send, so someone from the purchasing department overlooked the E-Mail, which contains the work task of the valve order. After 2 weeks I want to know, why there is no final order for the sampling valve, so I have to make many phonecalls, to get to know where the task is stuck and in a worst-case scenario the valve is too late at the construction site.
With the graphical workflow representation I would know, with only one mouse click, that the purchasing department forget to talk to the supplier, or in best case scenario, the purchasing department looks at the morning in his workflow representation and knows that he should talk to the supplier to negotiate the delivery conditions and after that he sends the taskfor approval to the next step of the workflow.
I think this improvement would make work life a lot easier and I also hope, that my suggestions is cleary enough defined, because I am from Germany and my language skills could also use a kind of improvement ;)

Kind regards

When trying to user psremoting you have to add a trusted host to your client's trusted hosts. This is fine and we normally default to '*' for developer machines that need to talk to prod and other infra. The problem is that this also requires the developer machine to start the winrm service which 'allows the computer to recieve Windows Powershell remote commands that are sent using the WS-Management technology'. I get pushback from devs who don't want to run this server service and see it as an unecessary security risk. We typically don't need CredSSP or have issues with the double-hop problem, so it doesn't make sense that when configuring the client to require that the server is started. I'd expect that a security review would also flag this as an issue for concern.