Error seen when attempting to add a new domain controller to an existing domain;
Verification of replica failed. The specified domain {Domain-Name} is still using the File Replication Service (FRS) to replicate the SYSVOL share. FRS is depreciated.
The server being promoted does not support FRS and cannot be promoted as a replica into the specified domain.
You MUST migrate the specified domain to use DFS Replication using the DFSRMIG command before continuing.
Solution: FRS is Depreciated
Before proceeding you MUST ensure all your existing domain controllers are AT LEAST Windows Server 2008. Your domain and forest functional levels should be at Windows Server 2008 (AL LEAST). It would also be a good move, to make sure all your DCs are replicating cleanly.
You need to go to one of your legacy (existing) domain controllers, and carry out the following PowerShell procedure.
First make sure that no one’s messed about with this before, issue the following command and make sure the migration process has not been previously started;
[box]
dfsrmig /getglobalstate
[/box]
Start the process.
[box]
dfsrmig /setglobalstate 1
[/box]
It can take a while, (even if you only have one Domain Controller!) Keep checking the status, with the command ‘dfsrmig /getmigrationstate’ until it says all the domain controllers have migrated to global state ‘Prepared‘.
Change the process to state 2 (Redirected).
[box]
dfsrmig /setglobalstate 2
[/box]
This typically completes a bit faster than the first state. Keep checking the status, with the command you originally used, until it says all the domain controllers have migrated to global state ‘Redirected‘.
Change the process to state 3 (Eliminated).
[box]
dfsrmig /setglobalstate 3
[/box]
As before, keep checking the status, with the command you originally used, until it says all the domain controllers have migrated to global state ‘Suceeded‘.
On the ‘Old‘ domain controllers, you need to disable the NTFRS service and stop it.
You want to Setup FTP on your Windows Server, (and more importantly make it work without disabling the firewall.) Below are the procedure you will need to carry out.
Note: For older Windows Operating systems like Server 2012, click here, or for Server 2008, click here.
Setup FTP Server (Windows Server)
Setup FTP on Windows Server 2012 (Including firewall setup)
Setup FTP on Windows Server 2008 R2 (Including firewall setup)
Firewall Configuration for FTP on Server 2008 R2 (Included in the Video above).
>
Related Articles, References, Credits, or External Links
We had the ‘run as’ service way back in Windows 2000, so the concept of running a command window ‘as administrator’ should not be difficult to understand. But the amount of times I tell people ‘You need to run that as administrator’, and they reply ‘I AM an administrator’ is far too high. With PowerShell theres no way of knowing, and with command prompt the differences are subtle.
Solution
There’s a myriad of different ways to launch an administrator command window, here are a few, If I’ve missed any let me know.
Launch Powershell in Administrative Mode
Powershell administrative mode (from Within Powershell)
If you’re already in Powershell you can open an administrative Powershell window, with the following command;
[box]
Start-Process PowerShell -Verb RunAs
[/box]
Powershell Administrative Mode (from Start Menu)
Option 1: From Start/Search > Powershell > Right Click Windows PowerShell > Run as administrator.
Option 2: Start > Right Click Windows PowerShell > Run as administrator.
Option 3: Start > Windows PowerShell > Windows Powershell > Run as Administrator.
Option 4: Right Click Start Menu (or Press Windows+X) > Window Powershell (Admin).
Launch Task Manger > File > Run new task > Powershell > Tick ‘Create this task with administrative privileges’.
Powershell Administrative Mode (from Windows Explorer)
From Windows Explorer > File > Open Windows PowerShell as administrator.
Launch Command Prompt in Administrative Mode
Administrator Command Prompt From Start Menu. (Windows 10 and Server 2016/2019)
From the Start/Search option > Type cmd > Then right click Command Prompt and select ‘Run as administrator’.
Command Prompt (Admin) – Windows 10 (& Server 2016/2019)
Right click the Start Button > Command Prompt (Admin)
Command Prompt (Admin) – Windows 8 (& Server 2012) Quick Links Menu
Press Windows Key+X > Select Command Prompt (Admin)
Administrator Command Prompt From Start Menu. (Windows 8 and Server 2012)
If you have the new Windows 8/2012 Start Menu (that we can’t call Metro any more) then type ‘command’ in the search window, then either right click and select ‘Run as administrator’, or press Ctrl+Shift+Enter to launch.
If you have the traditional start menu enabled or are running Windows 7/Vista, you can type command in the search/run box, then
Create An Always Run As Administrator Command Prompt Shortcut
1. Right click and empty area of your desktop > New > Shortcut.
2. Set the location to ‘cmd’ > Next > Call it Admin Command > Finish.
3. Right click your new shortcut > Properties.
4. Shortcut > Advanced > Run as administrator > Apply > OK.
Launch Admin Command Prompt from Task Manager.
Launch Task Manager (Ctrl+Shift+Esc) > File > Run new task > cmd > Tick ‘Create this task with administrative privileges’.
Launch Command Prompt ‘As Administrator’ From Command/Run.
I’m not a fan of this, in fact I only include it here for completeness, you can call a command windows and run it as administrator from command (or the run box (Windows Key+R). The reason I don’t like this is, you need to enter the machines local administrators password for it to work.
[box]
runas /user:%computername%administrator cmd
[/box]
If theres any I’ve missed feel free to drop me an email, and I will update the article.
Related Articles, References, Credits, or External Links
Process edgetransport.exe () (PID=6156). Object [CN={mailbox database name},CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN={domain},CN=Microsoft Exchange,CN=Services,CN=Configuration,DC={domain},DC=com]. Property [PublicFolderDatabase] is set to value [{domain}.org/Configuration/Deleted Objects/Public Folder Store (EXCH2K3) DEL:b60ef8b9-09dd-41c5-9aec-af2a4cc4f33e], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.
In my case I had a mailbox database that was looking at a public folder database, that no longer existed. (It was on the old/removed Exchange 2003 server).
Solution
Disclaimer: OK this error comes in a lot of forms, and references lots of different processes other than edgetransport.exe. I tried all the stuff I found online to try and fix the problem. But non of them worked, (this error gets logged when the Exchange services start).
In the end I fixed it myself, and it was annoyingly easy.
1. Look in your error message to see the “Mail Database” that’s complaining, (In this example it’s called “Mailbox Database 1507786053”).
2. Launch Exchange system Manager > Organization Configuration > Mailbox > Database Management > Select the offending database > Right click > Properties > Client Settings.
3. Under “Default Public Folder Database” > Browse > Locate and select a live public folder database.
4. Then restart Exchange services (Or reboot).
Related Articles, References, Credits, or External Links
Seen on Windows Server 2008 R2 running on VMware ESX/ESXi 4.0 and 4.1
Solution
Firstly, I’m assuming you are running the latest version of VMware tools on the machine in question, this procedure was carried out with VMware tools version 8.3.2 and cures the problem.
1. On the affected VM Click Start > In the search run box type > devmgmt.msc {enter}
2. Expand “Display adapters” Right click the one in use > “Update Driver Software.”
3. Browse to ” C:/Program Files/Common Files/VMware/Drivers/wddm_video” > Next.
4. When finished it should say “VMware SVGA 3D” Drivers have installed successfully. > Close
5. You will be prompted for a reboot, do so.
Note: Also ensure that you have allowed at least 8MB RAM for the graphics card (machine needs to be powered off before you can edit this).
Related Articles, References, Credits, or External Links
ES! it is, if in doubt see the compatibility matrix. But you have tried to install it and seen an error?
Error: This product can only be installed on the following 64-bit operating systems: Windows XP SP2 or above Windows Server 2003 Windows Server 2008
Solution
Essentially this just a bad error message that bears no resemblance the the actual problem!
The REAL REASON you are seeing this error is because you re trying to install vCenter on a domain controller.
This happens because, as part of the vCenter 4.1 setup the following takes place,
And if the server is a Domain controller, ADLDS cannot be installed. You will notice that if you watch the “Roles” section during the install of vCenter, that a role drops onto the list.
Final Thoughts
For anyone who thinks “Well Ill put vCenter on first then make the server a domain controller”. That won’t work either, if you try that you will see this error,
Error: The TCP ports shown below are required by Active Directory Domain Services, but are already in use on this computer. 389 ldap
To be honest a more descriptive error message would help. (Cheers VMware!). It’s not as if you cant do it…
Same thing on Server 2008
Related Articles, References, Credits, or External Links
This article is primarily geared towards making your guest virtual machines hard drives LARGER, If you want to SHRINK or make the drive smaller then see the following article.
1. On the properties of the VM select the hard disk in question and locate its size.
2. Enter the new size and hit OK. Note: Making the drive size smaller, will have no affect, if you want to do that clone the drive. If the option is “Greyed out” then make sure you DO NOT have any snapshots for this machine.
Re-sizing the guests “Volume” Option 1 – Graphically
Note: To do this using diskpart skip forward to number 10.
3. On the guest > Right click “My Computer” > Manage > Locate “Disk Management”. You will see there’s some free space that’s appeared on the end of the drive, (Click action > Re-scan if you can’t see it).
4. Simply right click the existing volume and select “Extend Volume”.
5. Next.
6. Copy in the extra space you want to assign (all of it probably) > Next.
7. Finish.
8. All the physical drive should now be committed.
9. And just to be sure, look in “My Computer” the drive is now 300 GB.
Re-sizing the guests “Volume” Option 2 – From Command Line with diskpart
10. Start > run > cmd{enter}
[box]diskpart list volume< select volume x –Where x is the volume number of the volume to be re sized[/box]
11. The final command is simply extend (This uses ALL the available free space.) Note the volume size in the picture below has jumped up by 40 GB.
Resizing a System (boot) Partition.
Server 2008 R2 and Windows 7 can do this quite happily. Older versions of Windows do not like having their system drive re sized, you see the following error if you try,
Error: The volume you have selected may not be extended. Please select another volume and try again.
Option 1 (Connect this drive to another machine)
In a virtual environment this is much simpler, but even if its a real physical hard drive, you can put it into another server and re size it. In an ESX environment simply do the following,
1. Shut down the machine that needs its drive re sizing, then go to another virtual machine’s properties and select add.
2. Hard Disk > Next.
3. Select “Use existing virtual disk” > Next.
4. Browse to the the drive we want to re size > Next.
5. Next.
6. Finish.
7. Now on the VM (Action > Re-scan disks). You will see the drive, and it’s not listed as a system drive, so you can extend it using any of the methods listed above.
8. For example, heres the drive re sized using disport.
9. when you have re sized the drive go back to the properties of the machine you have connected it to, and remove it.
10. OK.
11. Now power on the original VM and drive will be re sized.
Option 2 (Re size the Windows volume with GParted)
Note: This will work for a physical server as well.
1. Here’s our system drive with some nice shiny free space.
2. Make sure the server in question can boot from CD, in VMware do the following to boot to the machines BIOS, for a real server watch the screen as the server boots for instructions (Usually F10, F1 or Esc but differs depending on vendor).
3. Locate the boot order and make sure CD/DVD is at the top of the list.
4. Download GParted burn the image to CD, if you are working on a real server (use ImgBurn if your stuck). Or simply point the VM to the iso image, and boot the machine in question from it. At the welcome screen press Enter.
5. Use your arrow and tab keys to select Don’t touch the keymap > OK.
6. Pick a language.
7. We want to launch the GUI (X Windows), so select 0 (Zero).
8. Select Re size/Move > Drag the arrow to include the free space > Re size/Move.
9. Apply
10. Apply.
11. Close.
12. Click GParted > Quit.
13. Exit > Reboot/Shutdown > OK.
14. Remove the CD/ISO and press Enter.
15. The guest will run chkdsk the firs time it boots. This is normal don’t panic.
16. Once booted the volume will be re sized.
Shrink a Windows Partition with diskpart
1. To actually make the volume smaller with diskpart, the initial commands are the same.
2. If you use “shrink” on its own is will shrink the drive as much as it can (I cannot think of any situation where you would do this!). So to shrink the volume by 10 GB simply issue a “shrink minimum 10240”. (The figure in in MB).
Related Articles, References, Credits, or External Links
Any files or folders with the attribute “H” are not shown in windows explorer by default, if you would like to see them you will need to “show hidden files,folders or drives”
Solution
Windows 7, Windows Vista, and Windows Server 2008
1. Click Start > Control Panel.
2. Locate and Launch Folder options > View Tab.
3. In the “Hidden files and folders” section > select “show hidden files, folders and drives” > Apply > OK.
Telnet client from Windows, and have it as an “Optional Extra”. For most people that’s fine, but for anyone who programs network devices, or needs to test that ports are open, or test mail flow by telnet to port 25, that’s a pain.
