Tag Info

Hot answers tagged

15

I totally don't want to discount the rest of your question, but the path of least resistance is to replace the failed disks. When dealing with legacy equipment, there may be a temptation to devise an esoteric or clever workaround, but your immediate goal is to keep this particular hardware running in the current and stable state until you can migrate ...


5

There are settings in the Server 2008/2012 policies that aren't accessible on your 2003 server I believe, such as "Do not connect to any Windows Update Internet locations" under the Computer settings you show above. I believe the settings you are looking for in a 2003 environment are: Disable access to Windows Update The correct policy for v6 ...


4

First you have to make contact with your tape drive. Ultrium448 is a scsi one, but it has a linux driver, thus it can't be an issue. Probably you have to reach the tape disk on a char device. HP provides linux drivers for the task, if you have trouble, I suggest to ask detailed in a new question. The backups are coming with a .bkf extension. If this is the ...


3

Your question seems to be answered as "NO" here: Remote restart into safe mode? (windows) and f.e. http://answers.microsoft.com/en-us/windows/forum/windows_xp-networking/trying-to-use-remote-desktop-to-connect-to-a/16863a8f-f6e3-43d9-91f8-6c8fb9a1d077 However you could fire up your test machine to write the steps needed to be changed in safe mode and ...


2

If it's an AD account, then by "network hiccup" I would mean that windows is having trouble looking up the account, which sometimes happens when there's a connectivity issue. It might also be that your account doesn't have the privileges to look up a domain account (being a local account, perhaps?). However, my Adobe Flash Player Updater on my ...


2

Take the new machine. Install 2012 R2 as DC. Wipe one of the old DC, install 2012 R2 and make it a DC Wipe other old DC, install 2012 R2 and make it a DC Demote new machine (possibly reinstall it) and use it as web server. Remember to upgrade the domain functional levels. Done, without ever having only a single DC.


2

I've replicated this way before. It's just a zone transfer, really. I had to do it as part of a migration to new 2008 DC's in preparation for raising the functional level and replacing old hardware. The issue I had with 2003 was ad-integrated DNS not playing nicely. May have simply been because this domain had been an upgrade from NT 4.0 -> win2k -> ...


2

Edit: Please note the below only transfers A records and no other so you would still need to manually input remaining. I've never done the above, but another alternative would be to: export your A records and zones from 2003. Save it - c:\dnsrecords.txt re-importing into Server 2012. Replicate other 2003 settings on 2012 that covers external lookups. ...


2

Well one method that would completely avoid SMB, but would probably be fairly difficult to build would be based on iSCSI. Windows 2012r2 can be an iSCSI target, and Windows 2003r2 can act as a client. So you could setup a volume on the destination, and present it through iSCSI, then connect to it through your client system, and then mount the volume ...


1

mftar should according to the docs be able to read straight from the tape so ... mftar < /dev/st0 | tar tvf - If you'd rather grab the data off the tape first and then manipulate with mftar then you can use dd eg dd if=/dev/st0 of=output1 You might need to specify block size with dd. If you don't know how the tape was written then tcopy can give ...


1

Take the new server and install Windows Server 2012 R2 on it. Install the Hyper-V role. Create two new Windows Server 2012 R2 virtual machines on this Hyper-V server. Proceed with migrating AD from the old Domain Controllers to the two new Windows Server 2012 R2 virtual machines. Create a new virtual machine for the web server. IMO, there are very few ...


1

It's not possible to connect to a Windows 2003 server in safe-mode without 3rd party software. When entering safe-mode WITH NETWORKING, the OS will still block RDP connections. I've seen that VNC has been suggested as a 3rd party work-around but I can't confirm that it will work.


1

I had the same issue. Once I modified secpol.msc to these settings, it worked: Network security: LAN Manager authenitcation level - Not Defined Network security: Minimum session security for NTLM SSP based (including secure RPC) clients - Require 128-bit encryption Network security: Minimum session security for NTLM SSP based (including secure RPC) servers ...


1

I just solved this same problem on my cloned downstream servers. The GUID for replica downstream servers is held in the database. Install SSMS locally on the downstream server and connect to the WSUS database. Run this SQL: update [SUSDB].[dbo].[tbConfigurationA] set serverid=newid() Start the sync on the downstream server again - pretty much ...


1

Had same issue and I've found that my user was in Deny log on through Remote Desktop Services policy (in Security Settings > Local Policies > User Rights Assignment). After I removed him from this policy I was able to log on successfully.



Only top voted, non community-wiki answers of a minimum length are eligible