I have got some problems with one of my mailbox databases on my Microsoft Exchange Server 2016 server, its has been corrupt for some months without me could repair it and now it was time to remove the whole Exchange server from the organisation.
So i tested everything and search for some help and after some time i find out that you can force the removla of a exchange server mailbox database from the ADSI Edit tool.
Practical you telling the AD to remove the knowledge of the database with this hack.
- Start with log on to the Domain Controller
- From the start menu select run and enter adsiedit.msc and press run button.
- In the tool, right-click ADSI Edit and select Connect to.
- In the “Connection Settings”-dialog under “Select a well known Naming Context” select Configuration and click OK.
- Navigate to CN=Configuration [domain] → CN=Services → CN=Microsoft Exchange → CN=[organization] → CN=Administrative Groups → CN=Databases
- Identify the Mailbox Database containers that you like to remove and delete them.
Make sure that you are not deleting working mailboxes from the list, if you delete any by mistake you will have to delete & recreate the entire user using Active Directory Users & Computers.
I have a Raspberry Pi Zero Wireless that i have got to connect to my wifi direct on first bott (see this post) and then i liked to get the SSH activated from the first boot also.
After some searching i find out that you can put a file named ssh without any file extension in the boot partition.
Raspbian then going to activate SSH on the first boot so no need to put in any keyboard and monitor to activate it.
The content of the file doesn´t matter, it could contain either text or nothing at all.
Raspberry Pi Zero Wireless is a very nice Internet of Things computer but its only has mini-hdmi and micro-usb connectors wish make it not so easy to connect to configure to get it up on wifi but after som research i find out that it is possible to configure it to connect to wifi from the first boot of Rasbian.
Rasbian has built in that it copy wifi details from /boot/wpa_supplicant.conf into /etc/wpa_supplicant/wpa_supplicant.conf to automatically configure wireless network access.
If a wpa_supplicant.conf file is placed into the /boot/ directory, this will be moved to the /etc/wpa_supplicant/ directory the next time the system is booted, overwriting the network settings; this allows a Wifi configuration to be preloaded onto a card from a Windows or other machine that can only see the boot partition.
Since the /boot partition is accessible by any computer with an SD card reader, wifi configuration is now much simpler.
A skeleton wpa_supplicant.conf file can be as little as:
If you use WPA2-Personal settings with AES you can set the config file to have this text:
ssid=”Your SSID Here”
I can also recommend to read my post of how to activate the SSH on first boot, click here.
After some searching i find there is some commands that are differents between how people make there own windows installation usb stick, so i taked the one i got to work and write it here.
Start with put in a USB stick to the computer then you should open a command prompt as administrator.
When you have the command prompt you follow the steps below:
- LIST DISK
- Find your usb stick in the list
- SELECT DISK 1
- Replace DISK 1 with the number your usb stick has
- CREATE PARTITION PRIMARY
- SELECT PARTITION 1
- FORMAT FS=NTFS QUICK
Don´t close the command prompt.
Mount the ISO or put in your DVD disc so its comming up in “This computer” and remember the drive letter on it and on your USB stick.
Write in your command prompt:
- Where G: is your drive letter of your DVD-Rom
- CD BOOT
- BOOTSECT.EXE /NT60 H:
- Where H: is the drive letter on the USB stick)
Now you have a bootable USB stick, now you have to copy the windows installation files.
Now you have your own bootable USB stick with your windows installation, now you can restart the computer you like to install it on and setup the BIOS/UEFI to boot from the USB stick.
This is original taken from a tutorial for Windows 7 but i have personally used this tutorial for all kind of Windows versions (8, 8.1, 10, Windows Server 2012, 2016).