T
TheNuttyAdmin
Guest
I am the IT guy for a company in Charlotte that has 14 on-site desktops and 4 Windows 10 virtual machines. For over a decade, the virtual machines ran the company's POS software with Windows XP and Office 2003 without incident. However, the company moved to a new location in July, and I took this occasion to upgrade their hardware and migrate the company to Office 365. Since Office 365 doesn't work on XP, I bought 4 Windows 10 Pro licenses from Newegg and set up new virtual machines with W10 + O365 for the remote users. This is all being hosted via VirtualBox, by the way, because [reasons].
Three users have no problems whatsoever. However, one of the virtual machines shuts down randomly due to event ID 1074:
“The process C:\Windows\System32\RuntimeBroker.exe (COMPUTERNAME) has initiated the power off of a computer (COMPUTERNAME) on behalf of user DOMAIN\REMOTEVMUSER for the following reason: Other (Unplanned)”
The virtual machines are all logged in to the same domain under the same user. Since moving to hosted Exchange in 2011, I've used the same username, since the only thing that differs on each VM is the Outlook profile and the login for their POS app; it's a lot less work than creating a new user profile every time.
In this thread I discussed everything I'd done to that point: moved the VM to a different server, cloned a working VM and entered the user's O365 and POS accounts, did in-place reinstalls of Windows 10 on the host and guest, created a new AD user, upgraded to the October Update, deleted the VM and created a new one from scratch, etc. And NOTHING has stopped these daily 1074 shutdowns.
On Monday I took one of the company's old desktops - which I reformatted back in July - and set it up for this user. And it shutdown this afternoon, with the same error message. Frankly, I don't even know how it's possible for RUNTIMEBROKER.EXE to be shutting down a computer under all these circumstances: old virtual machines, new virtual machines, new physical machines. Seems like the only thing all these have in common is the Office 365 account.
I have a support ticket in with the Office 365 team, but I have no confidence that they'll be able to solve the problem. Googling this problem comes up with almost nothing. Is there ANYONE out there that can help?
Thanks!
More...
Three users have no problems whatsoever. However, one of the virtual machines shuts down randomly due to event ID 1074:
“The process C:\Windows\System32\RuntimeBroker.exe (COMPUTERNAME) has initiated the power off of a computer (COMPUTERNAME) on behalf of user DOMAIN\REMOTEVMUSER for the following reason: Other (Unplanned)”
The virtual machines are all logged in to the same domain under the same user. Since moving to hosted Exchange in 2011, I've used the same username, since the only thing that differs on each VM is the Outlook profile and the login for their POS app; it's a lot less work than creating a new user profile every time.
In this thread I discussed everything I'd done to that point: moved the VM to a different server, cloned a working VM and entered the user's O365 and POS accounts, did in-place reinstalls of Windows 10 on the host and guest, created a new AD user, upgraded to the October Update, deleted the VM and created a new one from scratch, etc. And NOTHING has stopped these daily 1074 shutdowns.
On Monday I took one of the company's old desktops - which I reformatted back in July - and set it up for this user. And it shutdown this afternoon, with the same error message. Frankly, I don't even know how it's possible for RUNTIMEBROKER.EXE to be shutting down a computer under all these circumstances: old virtual machines, new virtual machines, new physical machines. Seems like the only thing all these have in common is the Office 365 account.
I have a support ticket in with the Office 365 team, but I have no confidence that they'll be able to solve the problem. Googling this problem comes up with almost nothing. Is there ANYONE out there that can help?
Thanks!
More...
