JdL wrote:You are probably wasting more $/hour trying to retrofit SBS to work, than you would spend by just buying Server 2008 R2. This is the wrong tool for the job.
Stop wasting your time and get Server 2008 R2.
Show your purchasing mgr how you can be more productive with the time you save, and also how much better the server will perform.
Welch wrote:Here is a suggestion that would render you with virtually zero down time and allow you to get that box installed with 2008 r2. Ive done this with a Dell PowerEdge 840 before that was running raid 5.
Grab a copy of a Acronis backup and recover 10 or 11 (bootable) and an external drive large enough to make an image of the system. Do a complete full backup and restore that image to another computer that can act as your server for a couple of days (using the universal restore feature). Once the temporary system is in place and everything checks out, clean off your real server and slap 2008 r2 on it. Configure it and then go about migrating your AD and other settings/data.
I did this with a normal desktop out of desperation once for a dental office and they didnt even notice their server had been changed for a week when i came in to put the real one back in.
absurdity wrote:Once you've done a migration over to 2008 R2, you'll probably want to loop back and clean out a lot of the GPOs that SBS puts in place, and restructure ADUC a bit. Nothing critical, but I like to be tidy.
Welch wrote:absurdity wrote:Once you've done a migration over to 2008 R2, you'll probably want to loop back and clean out a lot of the GPOs that SBS puts in place, and restructure ADUC a bit. Nothing critical, but I like to be tidy.
Speaking of which, how intrenched in GPO's and other network goodies is your current server? If its nothing other than a basic AD for logon, you could always just manually rebuild the 20-25 users. Just a suggestion as I found it easier than dealing with a migration and some of the left over/changed settings.
Jason181 wrote:DrDillyBar wrote:Using Google means I have no role there.
and RAM is not really a problem.
You talk about a backup script, can you elaborate on this issue?
Forge wrote:There's also some black box magic going on which uses the backup to make a VM, I'm told, and the backup and/or VM is being periodically uploaded to offsite storage.
Forge wrote:There's also some black box magic going on
LaChupacabra wrote:Forge wrote:There's also some black box magic going on which uses the backup to make a VM, I'm told, and the backup and/or VM is being periodically uploaded to offsite storage.
The builtin Windows Server Backup feature stores a bare-metal backup as a vhd. If it is doing that I can't see any reason why there needs to be any kind of custom script. If you want to upload the bat/vbs/ps1 file that is doing the actual work for the script it should be pretty easy to figure out what is going on.
I also ran into a problem like this with a client and it turned out to be the logon script and how it was sharing printers that was crippling the server. Are there any other custom scripts running on the system?
Forge wrote:..."The boss doesn't have admin rights, though. "...
Forge wrote:You didn't read my first post, I'm guessing? The server itself CAME with a 2008 R2 license. What I don't have right now is the time to tear it down and put plain old 2008 R2 on there. I also can't have downtime on the server ATM, since we're on AD.
Forge wrote:I just need to make it run a little better in the meantime.
Users browsing this forum: blahsaysblah, Google Adsense [Bot] and 9 guests