DrCheese Posted February 28, 2011 Posted February 28, 2011 haha, not as bad as assessment manager which shows as "assman.exe" in taskmgr
mthomas08 Posted February 28, 2011 Posted February 28, 2011 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.
Tunster Posted February 28, 2011 Posted February 28, 2011 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. Ditto here! Our main server hasn't been updated, but by the looks of all the R2 servers running in Hyper-V off of it, they all updated with no problems (only thing is that it takes an hour and more to update!). 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.
mthomas08 Posted February 28, 2011 Posted February 28, 2011 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.
Arthur Posted March 7, 2011 Posted March 7, 2011 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.
jc1875 Posted March 7, 2011 Posted March 7, 2011 SP1 is available on wsus tomorrow (8th march) Description of Software Update Services and Windows Server Update Services changes in content for 2011
zag Posted March 8, 2011 Posted March 8, 2011 Has anyone had any problems with Creating/copying folders and getting a "file is no longer available" message?
AngryTechnician Posted March 8, 2011 Posted March 8, 2011 I've seen that (rarely) before SP1. I had hoped it would be fixed, but apparently not?
sted Posted March 8, 2011 Posted March 8, 2011 Availble now on WSUS would anyone trust it to wsus with the time it takes to install teachers/users would probably just think its crashed and turn off the pc requiring a rebuild
jc1875 Posted March 8, 2011 Posted March 8, 2011 would anyone trust it to wsus with the time it takes to install teachers/users would probably just think its crashed and turn off the pc requiring a rebuild I'll let you know shortly
Gatt Posted March 8, 2011 Posted March 8, 2011 I'm going to pick about 6 non-essential PCs and deploy it to see how well it goes, Though I'm planning on waiting until April Hols before releasing it into the wild...
jc1875 Posted March 8, 2011 Posted March 8, 2011 (edited) RDP'd into client machine and forced update from wsus 8 updates including SP1 Service Pack Installer started at 20:35:50 Service Pack Installer finished at 20:52:44 Restart takes 1 min 30s. /edit: not quite finished - rdp's back in and it's on stage 3 of 3, assembling service pack. expecting a long wait Another reboot and finished at 21:14 Edited March 8, 2011 by jc1875
SYNACK Posted March 8, 2011 Posted March 8, 2011 This is why I enable WOL on all my clients, release the patch at the end of the day. School wide reboot at 8pm, 11pm, 1am by which point it has worked its way through the updates. If the teacher has unplugged it/switched it off then it is their own fault that they have to wait.
Arthur Posted March 13, 2011 Posted March 13, 2011 Here's another gotcha. This time with MDT 2010 Update 1 and the latest WAIK. http://blogs.technet.com/b/mniehaus/archive/2011/03/12/issue-with-mdt-2010-update-1-and-windows-aik-for-windows-7-sp1-supplement.aspx With the release of the Windows AIK for Windows 7 SP1 supplement, there is a new version 3.1 of Windows PE available. If you plan to install this update, you need to be aware of an issue when using this with MDT 2010 Update 1. The actual error will look something like this (repeated for each Windows PE feature pack): Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7600.16385 Processing 1 of 1 - Adding package WinPE-HTA-Package~31bf3856ad364e35~x86~~6.1.7601.17514 [color="red"]Error: 0x800f081e[/color] [color="red"]The specified package is not applicable to this image.[/color] The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Exit code = –2146498530 DISM /Add-Package failed for component C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-hta.cab, rc = -2146498530. Uh oh – you can’t get past this error to generate boot images. So what should you do?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now