This could be just me but I've updated 2 laptops to sp1 and I've noticed that UAC has been turned back on. I'm looking into it more as it causes SIMS update issues.
Oh... SIMS PERM...
haha that damn file name, i've run it with the projector on infront of a bunch of kids before and they all laughed at what i was typing
haha, not as bad as assessment manager which shows as "assman.exe" in taskmgr
Glad other people have updated and no trouble so far.
I have R2 2008 Enterprise x64, I wil update this and the Hyper V servers on it.
Fingers crossed, glad some of you said it takes a while, I will start this on one of the servers as a test (which doesnt get used at the mo).
Great info all.
Glad none of them are functioning servers yet and are in testing (with our new network array storage) with preparation to go live over the Easter holidays.
First casualty, EPO has stopped working, just sitting there not loading the login screen.
I might have to have a play around and perhaps resort to snapshot restore.
FIX: Poor VM Performance & Errors with VMware Workstation 7.1.3 after applying Microsoft Windows 7 SP1
This is an issue which will likely have been affecting those of you, like myself, who upgraded their Windows 7 PC to Service Pack 1 and also run VMs under VMware Workstation 7.1.3 from the same PC. The introduction of the ‘Dynamic Memory’ (a new memory management ‘enhancement’ which allow for higher VM densities within Hyper-V – see here and here for more details) feature in the recent Microsoft Windows Server 2008 R2 and Windows 7 Service Pack 1 (SP1) release appears to have affected how Windows (Win7 and W2K8 R2) handles it’s memory. After installing this service pack on your VMware Workstation host PC you may likely experience memory allocation issues and poor performance when trying to run your VMs. Symptoms observed so far range from very slow performance of the VMs (W2K3, W2K8, Win 7 mix) through to the occasional BSOD, also a common error you may receive mentions failed memory allocation.
This memory issue, which definitely appears to have been introduced with the release of Windows Server 2008 R2 and Windows 7 Service Pack 1, is clearly affecting the wider VMware Workstation Community, as can be seen in this VMware forum thread here. There isn’t an official patch fix at the time of writing this post though there is a setting which can be applied to your VMware Workstation install which from my testing so far seems to alleviate the issue. If you are also affected with this memory problem then you may also want to consider adding the following parameter:
Edit the ‘config.ini’ file which can be found here: C:\ProgramData\VMware\VMware Workstation\config.ini
Add the following line to the config file: vmmon.disableHostParameters = "TRUE"
After adding this line to the ‘config.ini’ then reboot your host PC for this setting to take effect. You can’t beat a good old reboot after changing settings such as this.
Has anyone had any problems with Creating/copying folders and getting a "file is no longer available" message?
I've seen that (rarely) before SP1. I had hoped it would be fixed, but apparently not?
Availble now on WSUS
There are currently 1 users browsing this thread. (0 members and 1 guests)