If you are sick of seeing files put onto shares that should not be put there use the File Server Resource Manager (Ressourcen-Manager für Dateiserver) to block this.
You can set up presets to block different file types. Use this templates by adding a new loal path and chose your preset. That also blocks the access on network share level.
You can also activate the mail option to be informed, as administrator, or to automaticly inform the user by mail, so they are not wondering what the reason for not beeing able to put the file to the share might be.
vCenter error on different occasions without reason: The operation is not allowed in the current connection state of the host.
You are trying to migrate a vm and the selected host is not compatible vcenter tells you?
Error in en: The operation is not allowed in the current connection state of the host.
Fehler in de: Der Vorgang ist im aktuellen Hostzustand nicht zulässig.
But you are sure you know better? But you cannot reboot the host or operations are still taking place?
Right click the host, disconnect it and reconnect it.
Give it another try.
NOTE: For vCenter version < 6 this HowTo should work out.
From time to time it might happen that you are asked to change vcenter ip address.
Do not think that you could do that by using the console, so no need to move over to the rack. After deployment you are not allowed to change the management network settings from console.
So, what you do is:
- add a new nic to the vcenter vm in your vm settings, probably on ESX
- set the IPv4 / IPv6 settings as required in "system configuration -> network" inside your vcenter
- reboot the vcenter vm
- delete the old nic, probably nic0, from your system configuration
Check wether your vcenter is reachable on its new IP address.
You are done now.
So, if your Outlook is not finding any search results in an Exchange environment it might be the database needs reseeding. Make sure "Microsoft Exchange Search" and "Microsoft Exchange Search Host Controller" services are up and running. If they are, start the Exchange Management Shell and read the database status by executing "Get-MailboxDatabaseCopyStatus *".
Important here is the "ContentIndexState" - so here it should say "healthy". If you got something other than that, get the Index rebuild by:
- stopping above mentioned "MS Exchange Search" and "MS Exchange Search Host Controller" services
- opening the file location of the affected database
- thinking about what would be if you mess things up and you got no backup
- finding the only folder in your databases folder with a long cryptic name (e.g. located under "C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database XYZ´") that contains 3 folders named "indexmeta", "Journal" and "ms".
- deleting that folder
- restarting both services
- getting an "healthy" or "crawling" status on the affected database by again checking "Get-MailboxDatabaseCopyStatus *"
The bigger the database the longer it will take to get "crawling" finished and a "healthy" status.
A driver problem is causing problems when using HP Broadcom NICs on Hyper-V enviroments. The VMQ engine is distributing network traffic to guest machines. A buggy driver is causing high latencys and very low and varying network throughputs to guest machines. You should update that driver. HP is offering a working driver on their support site. Download an install the driver on the host system.
For MS Server Core Installation, install the driver through console "pnputil.exe -i -a DRIVER.INF" directly on the host.
Give it a restart and get a fresh cup of coffee so you are ready for the next obscure things that might occure.