Tag Info

Hot answers tagged

18

There's no simple solution to this - its probably going to be a long and annoying road to getting everything moved. I'd start with a few things, but the book I recommended in the comments likely goes into a few details. I see four main stages here - inventory, redeployment, testing, and acceptance. What am I hosting right now If you haven't already, do ...


6

I would advise (temporarily) setting up your new domain on Server 2008 R2, as I've done with my current employer's new forests. Set up your new forest on a (temporary) Server 2008 R2 domain controller. Join your Server 2012 server to the new domain, and promote as a domain controller. Transfer all FSMO roles to the 2012 Domain Controller. "Migrate" SBS ...


6

Some of the potential attacks involve putting a rogue router or DHCP server on your network. The best protection is to let the L2 switches filter the traffic. If a switch port goes to a workstation it probably should not send out packets that usually a DHCP server or a router would send. If you want such protection you should look at the protocols that the ...


5

Microsoft has published a blog post somewhere that I can't find at the moment stating that a new version of ADMT will be released in Q1 of 2014 that will support installation on, and migration to/from, any currently supported version of Windows Server. So, you have three options: Shell out cash for Quest tools which don't have this restriction Install a ...


5

Live Migrate the guests to a single host if you have the capacity. Reinstall the now empty host with 2012 (R2 hopefully). Live migrate all the guests to the 2012 server, reinstall the second server with 2012. Balance the guest workloads. If you don't have the capacity to do this, then yes - buy new hardware.


5

It depends on whether you want them to do anything IP-aware. An ethernet frame is an ethernet frame is an ethernet frame, as Gertrude Stein didn't say; a good switch will repeat it based on MAC addresses without caring what the payload is, so if that's all your switches do - layer-2 stuff like VLANs and port-mirroring - you should be fine regardless. The ...


4

Don't do this. You can keep your administrative burden lower by keeping these users in the same domain, especially since they're going to be in the same forest and exchange org. Per this link ...


4

If all you truly have is "Outlook Anywhere" access, then I'd presume that you don't have access to administer the Exchange Org in Forest A. If that's the case, then you'll need to manually migrate, which won't be fun with a lot of mailboxes. You'll also be dealing with issues related to if you have public folders, GAL issues when it comes to replies to ...


4

All of these issues can be resolved by deploying a secondary domain controller Full Stop. You should have at least two domain controllers available. Trust me. You really want at least two domain controllers. I think if you spend a bit of time reading about Active Directory design and how it works and you will see that multiple domain controllers should ...


4

Use the native tools, assuming you have a vCenter. You could perform a live-migration or cold-migration (change host and datastore), depending on your license level. However, vCenter may not be happy if the DC is down. Do you only have one domain controller?


3

From what you're describing you really, really, REALLY need to rearchitect your AD design. Like HopelessN00b pointed out, Active Directory has a concept of a "site", which is the correct logical representation of sites within the same company (domain of control). Your AD should also be properly scoped (as ad.mycompany.com or something similar). Properly ...


3

do I have to upgrade to 2010 first, then from 2010 to 2013? Yes. This is basically the price of not upgrading for a long time - and then hoping MS would care about it. 2 generations is the biggest supported. So, you need an interim step.


3

I never had issues using Clonezilla in terms of network drivers. It always worked for me.


3

I would say you have a lot more to consider than just hard drives. You are intending to transfer to a completely different virtualization package, which will take much more than a days worth of work. Theoretically you would need to: - Transcribe the VM configurations (more than likely by hand) from Microsoft's spec to QEmu's spec. - Convert the VHD images ...


2

If you have shared storage, make sure the VM's disk is located on the shared storage, accessible by both hosts, and mounted in the same mountpoint. Then standard, libvirt-directed live migration will simply work. If you don't have shared storage, KVM/QEMU supports that as well. In more ways than one, in fact [1] It is, of course, a better idea to use ...


2

Perforce knows Git-SCM, so it should theoretically be as simple as creating a new remote, and pushing with the -a flag. A git repository is simply a git repository, regardless of where it is hosted at, in general. (There are exceptions, such as Heroku, and Perforce may be one of those exceptions.) If this does not work... what have you tried so far?


2

ok this answer appends to grs's answer. so credits do go there for 70% of the answer. Notes: if this answer suits you , GET a backup NOW. if you own a UPS connect it on the pc in question NOW. The following procedure was carried out in linux, on DATA disk arrays. It may need some modifications to work on OS/boot arrays. The following procedure requires ...


2

You would need to update the u1 size before increasing the filesystem from within the OS. The latter will not "see" the new size until the 3ware controller notify it. The unit capacity expansion in 3ware is called migration. I am certain it works for RAID5 and 6, didn't try it with RAID1. Here is an example of migration command to run: # tw_cli /c0/u1 ...


2

Make sure you have the 7-zip command line version installed; it's separate from the GUI. YOu can download it here: http://www.7-zip.org/download.html


2

The Exim Book gives an example of manualroute with user part lookups 5.6.1 Using a manualroute router Below please find it modified to your needs (based on 7.4 The manualroute router in the book): exchange_people: driver = manualroute domains = example.net ## limit router to addresses in example.net domain local_parts = lsearch;/etc/e_users ...


2

Restoration isn't my main problem as the image will be a backup of last resort that will only last until the OS is migrated, it's taking the image and saving it quickly over the network. All of the below operate or can operate as LiveCD's. Clonezilla is popular, and SystemRescueCD has a variety of utilities and network drives, incluing PartImage for ...


2

Log into oldserver and run tcpdump/wireshark. Any client connecting to oldserver over mail ports (25/tcp smtp, 110/tcp pop3, 143/tcp imap, 465/tcp smtp ssl, 995/tcp pop3 ssl, 993/tcp imap ssl) needs to be reconfigured. The other thing you could do to force everyone over to to make a DNS CNAME record from oldserver point to newserver.


2

I have read about ADMT but doesnt work on 2012 and 2008 as far as i can tell.... any suggestions? This is no longer the case. You can install the latest ADMT 3.2 and PES 3.1 bits on 2012 and 2012 R2 as well as migrating to 2012/2012 R2 based domains with it. This is your tool of choice. That said, as @voretaq7 has pointed out, you seem to have larger ...


2

If you want to stay on the supported path: migrate to Server 2012 Essentials transition to Server 2012 standard set up trusts to the destination domain set up Server 2008 R2 DCs in source and destination domains (unless a newer version of ADMT supports Server 2012) Use the 2008 R2 servers to migrate your domain using ADMT You might consider taking a ...


2

You can do this a few ways: Use a proper backup application that can do a full backup of your server and do a bare metal restore to dissimilar hardware. This will literally move everything. Move your data and config, i.e. /etc and /var but note that if you are using different versions of CentOS on each server, the syntax for config files may have changed ...


2

Exchange 2007 and newer versions stop you from performing a domain rename. Since you say that you're ditching on-premise Exchange that's not a factor. That opens up the door for what I think would be a much easier process than any kind of creation of a new forest or domain: Complete your migration to Office 365 and remove Exchange from your SBS 2011 ...


2

I know this doesn't look really good as an answer and I apologize in advance... but it happened to me exactly this way: for unknown reasons, sometimes an IMAP migration might just get stuck and not proceed at all. Try canceling it and starting it again. Sadly, I'm no kidding here: when it happened to me, I even opened a support call with Microsoft. After ...


2

Create a new AD/DNS first on the new VM from scratch. You really want two of those in your environment if possible. Afterwards migrate the physical server to Hyper-V. I dont know what your using for DHCP but consider editing it to point to dns on the new VM you create. If users are using AD to login to there systems having the second AD server up wont ...


2

That's not how you migrate virtual machines between ESXI hosts, no. The proper, supported way to move VMs between hosts without a reboot (and the only way that's likely to result in working VMs once you're done) is to use vMotion. Your specific setup and licensing entitlements will dictate a lot fo the details, but the easiest way is generally to create a ...


2

The user's data is dead and gone, yes. Microsoft support confirmed that the original, automatically generated encryption key is not retrievable, and is far too long to crack.



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