3 ways to tackle this:
- sc remoteMachine stop beep && sc remoteMachine config beep start= disabled
- sc stop beep && sc config beep start= disabled
- Net Stop Beep && Reg Add HKLMSYSTEMCurrentControlSetServicesBeep /v Start /d 4 /t REG_DWORD /f
Archive for the 'Server 2003' Category
Silly me, didn’t realise that NTFS had a limit of 2TB partitions (This is why you research.).
I have a Dell Poweredge DP500 with 6x 1TB disks.
My options:
Go Linux - not at this point in time. Though I seriously considered it.
Use GPT partitions (System drive cannot be a GPT drive, hence I lose some drives still)
What I ended up opting for was:
1x RAID 1 array for OS - 1TB
1x RAID 5 array for data - 3TB (Converted the disk to GPT)
So I lose 2 drives to redundancy in this config instead of the 1 I would have liked.
Ideally what needs to happen is:
- Manufacturers (maybe some do) to support EFI firmwares so we can boot GPT partitions.
- For them to make it well known that there is a limit when buying these items and configs.
*Update: Been told Server 2008 and Vista don’t have this problem but I don’t have licenses for those yet.
Good reading for this topic:
https://www.microsoft.com/whdc/device/storage/GPT-on-x64.mspx
http://technet2.microsoft.com/WindowsServer/en/library/4b35160a-4e27-4258-9e8b-e2088f8a757a1033.mspx?mfr=true
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23066074.html
http://www.carltonbale.com/2007/05/how-to-break-the-2tb-2-terabyte-file-system-limit/
NTBackup isn’t working and you’re getting errors like this:
Volume shadow copy creation: Attempt 1.
Timeout before function completed
Error returned while creating the volume shadow copy:0xffffffff.
Error returned while creating the volume shadow copy:ffffffff
Aborting Backup.
———————-
The operation did not successfully complete.
———————-
This is how I fixed it:
Continue reading ‘When NTBackup dies (or anything that uses the Volume Shadow Service (VSS))’
Boot into the Windows Recovery Console using the Windows CD-ROM or using the startup option (if available).
Type in the password for your installation of Windows, and press Enter.
When you see the C:\Windows Prompt, type this command:
DIR $*
This lists all the folder starting with the letter $. All the $NtUninstall…. folders are now displayed. $NtUninstall folders are nothing but the Hotfix backup folders, which contains the original version of the system files, before the hotfix was installed.
Note down the Hotfix numbers matching the date you installed the problematic Hotfix(es). Spot the Hotfix that you want to remove, and change to that directory by typing this:
CHDIR $NtUninstallKBnnnnnn$\spuninst
Example:
CHDIR $NtUninstallKB873333$\spuninst
Once you’re in that folder, you’ll need to execute the spuninst.txt which contains DOS commands, similar to a .BAT file. The command instructions in this spuninst.txt file will actually copy the original system files to their respective folders. To run the spuninst.txt file, type this:
BATCH spuninst.txt
The hotfix will be uninstalled. Restart, and see if the problem is resolved. If Windows loads normally, open Add/Remove Programs and completely uninstall that particular hotfix. This ensures that the additional files, Add/Remove entries and other registry keys added by the Hotfix are removed completely.
If Windows does not load, load Recovery Console again and then follow the above procedure to remove the additional Hotfixes one at a time, to isolate the problem. If you install multiple Hotfixes in a single session, it’s difficult to point out which of the installed Hotfixes is preventing Windows from loading. Hence you need to troubleshoot it on a trial and error basis, using Recovery Console.
Sometimes I forget to enable this. So I found this useful.
http://www.windowsdevcenter.com/pub/a/windows/2004/05/04/serverhacks_remote.html
To return to Legacy mode, run WDSUTIL /Uninitialize-server at a command prompt.