is the enterprise the same between these two MICROSOFT.SERVER.2008.R2.RTM.WITH.SP1.X64.VOLUME.E NGLISH.DVD-WZT and MICROSOFT.SERVER.2008.R2.ENTERPRISE.RTM.WITH.SP1.X 64.VOL.ENGLISH.DVD-WZT
I have installed SP1 and have tested it intensively. There are no issues with the OS itself, which means it boots as fast as ever, except there are more unused files now (I prefer a clean install of the OS with SP1 integrated later then). But: Since I have SP1 installed I have massive problems with filezilla / pageant.exe . I need to upload files to server(s), almost every attempt results to corrupted data error and I have to retry and retry..... My final result: If you want to avoid issues, do not install it. Never touch a running system. SP1 basically improves nothing! I don't know if it's a filezilla /pageant.exe issue or not, but it doesn't matter. Fact is that this SP1 was leaked before the official release, which means: If issues with applications should occur, the developer of the application cannot make an update therefore this time....so I have to uninstall SP1 or to wait for a filezilla / pageant.exe update. Or to figure if it is a network issue or..... This is of course no real problem for me, but I want to ask: Has anybody else issues with filezilla / pageant.exe, especially when uploading files? Thanks.
Hello all, I am novice and this will be my first post in this forum. The question is if Wzor Windows 7 with SP1 integrated Ultimate 32bit/64bit isos are final. Can anyone can confirm? Asking because some licenses are pre-release and after I installed by skiping serial number in installation procedure, Windows under System show me that until activation is 3 days, but there must be 30 days. This is other bug. Please friends confirm if it is final. Regards
That is no bug, that is in general the case. After the 3 days are over you get your 30 days. It was the same with Vista and Windows RTM and Server 2008 and Server 2008 R2 (though here you get 60 days instead of 30).
I installed the integrated version some days ago. But in Disk Cleanup I noticed some backup files which can't be deleted. Is that normal? This may have been discussed already, but reading 154 pages ain't so encouraging. thanks.
I just noticed after loading the SOFTWARE hive from the mounted wim that the packages key contains two sets of keys for each package - one for SP1 (6.1.7601.17514) and one for RTM (6.1.7600.16385). This is the same as what you get when you slipstream a service pack, although with this iso, after installation there are only one set of keys left. I loaded the SOFTWARE hive from a Vista SP2 WIM to compare and there was only one set of keys for each package. Has anyone been using DISM to remove packages manually? I keep getting an access denied error, even though I've taken ownership and given proper permissions to the package keys. I've deleted the owners folders as well, but to no avail.
on the wtz iso the disc cleaner shows the "backup files" but reports as 0mb and there are in fact 0mb, sp1 slipstreamed with rt7lite does hold the back up files but you have to boot from the DVD to remove them, boot select repair then open cmd prompt and I think you just type dism /online /cleanup-image /spsuperseded
I did a little experiment on a Virtual PC with a 20GB virtual drive: 1) I installed 7600 (x86-32). Free space on the drive: 13.8 GiB. 2) I turned off System Restore and installed the 7601 update. Free space on the drive: 13.1 GiB. 3) I ran the DISM cleanup. Free space on the drive: 13.8 GiB. 4) I wiped the virtual drive and did a clean install with an integrated 7601 image. Free space on the drive: 13.8 GiB. So if there is extra junk left behind after installing using the EXE and a DISM cleanup, it has to be less than 0.1 GiB. Of course, I still prefer a clean install of an integrated SP, but for existing systems, nuking-and-reinstalling is too much trouble, and as you can see, there is not much benefit.
wtf happened to the thread :| well, the ISOs are indeed NOT final, don't expect the same hash in MSDN or technet, I'm suspecting something fishy here.