Forum Replies Created
-
Posts
-
You can extract the “portable” Teamviewer from the installer using 7zip. This will run on Server 2008 and you won’t even need to install it. To do this you have to extract the downloaded Teamviewer installer twice. Extract, then extract the output a second time into a subdirectory. In one of those subdirectories you’ll find Teamvierwer portable which can be run by simply double clicking it. Very nice tool by the way ! Even my mother can run it, straight from the attachment I mail to her when she calls with a question that’s pretty hard to answer by phone to someone who doesn’t know what Explorer is and can’t find anything that isn’t an icon on the desktop.
I’ll answer my own question: yes, it works very well with AVG. Just make sure that you install _only_ the Comodo fiewall and no other feature.
Arris, Stukan, you’re both geniuses. This is the ultimate crack ! The whole thing can be automated with a simple script. Maybe add the registry mod to it to get AVG working but change the real key temporarily instead of making the fake one. No need to patch software kits individually anymore. Convert, install anything that installs on that other OS and convert back to Server again. Even my mother can do that. Fantastic !! Thanks a lot.
Does it work well with AVG ? Less than a week ago I tried Comodo on the NT 6 client version, it disabled AVG and AdAware. I would like a proper firewall but I like a virusscanner more.
There a sort of Vista type system restore possible without having to make complete images of the OS partition. I’ve only tested this a VM where it works, but usually if things work there they work on real hardware too. The only snag is that you cannot do it with the BOOT partition of the system. You can do it with any secondary OS installed. The next time you reinstall your machine, do it twice with the first OS going into a small partition. You can use a vLited 32 bit version for the first install. Depending on your memory and how much you can vlite out first it should easily fit in a 4-8 GB partition. Remove everything that can be safely removed without completely breaking it (printer drivers, languages, speech etc. use lots of space and can allways be safely removed, but theres much more). Don’t spend time pondering whether you should remove something you might need later on because you won’t be using that install for anything else than installing a boot partition and making/restoring shadow copies of the OS partition you install next. Install that and then install again the way you would normally do. The second OS will be the one you will actually be using. Shadow copies made of the second OS’s partition can be reverted back to if you boot into the first OS first, revert and then boot again normally, into the second OS.
The shadow copies can be made by the second OS while it’s running but this will give you a black screen saying that the OS wasn’t shut down properly when you revert using that shadow copy. Usually that isn’t a problem but it’s cleaner if you boot into the first OS to make the shadow copies (restore points) of the second.
I tested by making a shadow copy of the second OS then booting into it, clobbering the registry big time so it gave a nice blue screen upon reboot, then booting into the first OS to revert. The second OS booted perfectly again after the revert.
It will cost you the 4-8 GB for the boot partition but with nowadays disks that isn’t such an issue and you can have restore points in Server 2008 ! Made in a couple of minutes and reverted to in about the same amount of time. Just my 2 cents …You can make a slipstreamed install iso with SP2 but unless you already have experience with that and with all the necessary tools, it isn’t going to be something done in an evening. I struggled for days before getting it right. AFAIK there is no vLite version for SP2 yet. Either enjoy the learning experience or search torrents.
I did it using a VM. I used Sun’s VirtualBox. It’s much faster than MS Virtual PC and supports 64 bit OS’es. But any VM will do. Server 2008 has to be installed in the VM twice because you can’t use the boot partition (ie. the first installation) for the slipstream. You must use the second installation’s partition/virtual disk, without all the boot stuff on it for the slipstream. As soon as the second installation is installed and you’re logged into the admin account, reboot into Audit mode (run %systemroot%system32sysprepsysprep.exe). Just leave all the windows, including the sysprep window open. In audit mode mount the ISO file with SP2 on into the virtual CD drive of the VM and install SP2. Once SP2 is installed run compcln.exe to remove all remnants of SP1, then use the sysprep window to generalize and shutdown the VM: the window should already display OOBE, leave that. Select “generalize” and “shutdown”. NO REBOOT unless you have the Windows PE iso already mounted in the virtual CD. If the generalized partition boots, which it will fail to, you can start all over again. Boot the VM with Windows PE and make a new install.wim using, for example:
imagex /capture /compress maximum /flags “SERVERENTERPRISE” d: z:install.wim “Windows Server SERVERENTERPRISE”
where drive z: is a network drive connected to a share on the host machine. Note that the first string between quotes, just after /flags, must exactly match the edition you’re slipstreaming otherwise the install.wim file will be useless. What you between the second pair of quotes isn’t that important. You can find the correct strings by using “imagex /info install.wim” on the original instal.wim file or look them up on the Microsoft website. Use “SERVERSTANDARD” if you’re slipstreaming the Standard edition. I don’t know about Datacenter off the top of my head. Capturing the image can take up to an hour because of /compress maximum. Don’t worry, if you don’t /compress maximum you’ll win time with the capture but lose all of the time won later on time and again when you use vLite to add minor updates, drivers or remove components.
When the capture is finshed, replace the install.wim in the original iso with the one you just made. You could copy the contents of the original iso to a USB memory stick and replace the install.wim with the new one or use any tool to make a new iso. You’ll have to download the WAIK to do this first if haven’t done that yet and create a Windows PE iso with imagex installed on it. It doesn’t matter whether you use a VM or real hardware for the slipstreaming because the final install.wim file will be hardware independant anyway. I sincerely recommend VirtualBox. Using that was at least as fast as doing it on real hardware, and easier beacause everythings virtual. DVD’s, harddisks etc are all just files on the host. Even the network connection to the share is emulated and in fact is just a local file copy on the host machine. Just don’t install any VM specific drivers onto the slipstream partition because then you’ll end up with those in the final install.wim too. Maybe even on the real hardware later on, where it’s useless in the best case. Using a VM also makes it easy to make intermediate copies of the virtual diskfile so you won’t have to start all over again if you make a mistake somewhere, such as forgetting to run compcln.exe before generalizing :(. Doing that won’t ruin your install.wim but it will be close a gigabyte larger and may not fit onto a USB stick or a single DVD. Because the copied virtual disk hasn’t been generalized yet, you can also use it to add more updates without using vLite later or even convert server to a desktop in the VM and image that. Really, once you’ve done it yourself you might even start hoping SP3, 4 and 5 are released asap so you can do it again 🙂Arris, I just checked it in a VM I still had running x86 SP2, your patch works there as well. It was the least I could do in return. Thanks again.
