Skip to main content


Showing posts from 2017

O365: Skype for business 2016 - GPO for switching off splash screen

When you need to disable splash screen for users you, can apply group policy with preferences/register settings adding this key:
with value of 1.
Additionally, you need to have update installed:


Windows 10: my screen went black

In Windows 10 there are color filters feature controlled with shortcut.
If you mistakenly hit that Ctrl+Win+C, you will apply color filter, which default settings is Greyscale. Hit it again to turn it off.
That's it!

Exchange 2013 : Connecting disconnected archive mailbox

According to Microsoft, connecting archive mailbox after disconnection, should be easy as use connect-mailbox -archive command - similar as to use with regular mailboxes
But this will not work with Exchange 2013
Instead, yo need to use:
Enable-Mailbox -ArchiveGuid MailboxGuidHere -ArchiveDatabase DatabaseNameHere -Identity MailboxNameHere

2003: Cannot start server after cloning it - activation error

After cloning 2003 server, because of hardware change you can see information that you have to activate Windows.
Your system probably has no drivers installed, so you will not be able to connect to the network and activate it again.
The solution is to do workaround for the time of installing drivers.
This omits activation and let you install whatever you need before turning it back off.
1.Open your regedit RUN > REGEDIT
2.Find key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WPAEvents
3.see the string OOBETimer
4.Double click.change all content with this one FF D5 71 D6 8B 6A 8D 6F D5 33 93 FD
5.Right Click on WPAEvents(Regedit)and choose Permissions
6.Window will show up,click to System and check all of Deny Listbox
7.Restart Your PC

To complete your device settings, it's good to get rid of old hardware that is hidden now and cause problems.
Run command:
set devmgr_show_nonpresent_devices=1

Add Legacy driver to 2003 OS…

Powershell : How to export only errors from powershell command?

Sometimes, you need to export only the errors to your file, for example to show what needs to be corrected.

As you know, you can do an export from powershell cmd-let to a xml, csv or txt.
For example:
Get-Mailbox |Export-Csv .\mailboxes
Get-Mailbox |Export-Clixml
Get-Mailbox > mailboxes.txt

Additionally,  working in the loop, you can append data to the file, using -Append switch:
$users|%{Get-Mailbox $|Export-Csv .\mailboxes -Append}
But what to do in the situations when you need to export only errors in the current command?
For example you've created mailboxes according to the list, but then some of them were deleted.
One of the possibilities is to compare your list with errors from cmd-let.
You can do it manually, but it could be painful.
I propose you to use pipeline with using not well known switch >>.
This will output only errors to your txt file. $users|%{get-mailbox $_.userprincipalname |select displayname, userprincipalname} 2>>MailboxNotExists.txt Here are the swit…

Cannot open mailbox System Attendant

Today, Get-MigrationEndpoint error on local Exchange gave this error:

"Cannot open mailbox /o=XXXX/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=XXXXXX/cn=Microsoft System Attendant.

Standard checking for all arbitration mailboxes
get-mailbox -Arbitration

All mailboxes are in place. So this must be something else...

So, let's check database where this mailbox exists:
get-mailbox -Arbitration migration* |select database


Then, check database status:
Get-MailboxDatabaseCopyStatus databasename

OK, so now we can see that mailbox is sitting inside dismounted database.
If you mount it again, it'll fix this error.
But you can of course mount database and move the mailbox over to the desired database using:

New-MoveRequest  "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" -TargetDatabase databasenamehere

Powershell - how to get virtual machine GUID / ID (easiest way) from the hypervisor

Today, easy thing to manage, but of course - if you now how to do it.
To get VM ID from hypervisor, for example - to manage virtual machine from the powershell direct - you need to run simple command in the administrator session:

(get-vm virtualmachinename).id