anyweb

ok just to let you know that the server relocation and reinstallation is now complete the server was moved from amsterdam to sweden on friday, then reinstalled on saturday, and reconfigured today, Sunday and you are now viewing the site back in it's original server. 0 downtime and all data retained ! cheers niall

The Chris123NT blog thought it had found a critical bug in Windows 7's chkdsk utility. Run the tool with the /r switch (locate and repair bad sectors), and you should see memory usage for chkdsk eat up all your memory, or it crashes your machine with a blue screen of death. The original report only called it "critical", but people like Randall Kennedy (who else) labelled it as a "showstopper". As it turns out, this was all way overblown. First of all, this bug will not be seen when running chkdsk on your system drive, because Windows will offer to run chkdsk before booting the system. If you run it on a non-system drive, Windows will ask to unmount it and continue the check, or do it during the next boot. The bug will not appear in any of these cases. When running chkdsk on an external drive, for instance, memory usage can indeed spike, but an actual blue screen of death is very hard to reproduce. There are indications that certain outdated drivers may cause a BSOD to appear, and that updating said drivers to the latest versions fixes this behaviour. The eating of RAM is actually by design, as Sinofsky has explained: We haven't reproduced the crash and we're not seeing any crashes with chkdsk on the stack reported in any measurable number that we could find. We had one beta report on the memory usage, but that was resolved by design since we actually did design it to use more memory. But the design was to use more memory on purpose to speed things up, but never unbounded — we request the available memory and operate within that leaving at least 50M [reading other people's reports, this should most likely be 500MB] of physical memory. Our assumption was that using /r means your disk is such that you would prefer to get the repair done and over with rather than keep working. more > http://www.osnews.com/story/21964/Chkdsk_Bug_Anything_But_a_Showstopper

fyi, had some minor issues with php this afternoon (memory_limit) which are hopefully now resolved, and my server hoster has informed me that while they were reinstalling my server in amsterdam there was a hardware failure... so let's hope they provide me with a new one soon, i'll update here when i know more cheers niall

hmm have you tried importing the client computer into SCCM using computer associaton and see what happens then ?

should be fixed now, please test

ok i have now completed the first phase of the server reinstallation the mirror is created *this is it*, and dns is now pointing to the backup server, I will update this post later today cheers niall

is the timezone on the clients the same as the configmgr server ?

Step 5. Install the Application Virtualization Management Server Perform the following on the APPv Server: Browse the APP 4.5 CU1 cd to INSTALLERS\SERVER\MANAGEMENT and right click on Setup.exe and choose Run As Administrator to start the System Center Application Virtualization Management Server wizard, click next Accept the License Agreement review the Registration Information choose Custom as the type of installation Select the drive and install path you wish to use and verify that This Feature, and all subfeatures, will be installed on local hard drive is selected for each option and click next enter the SQL server name and click next the appv Database should automatically be selected, if not select it from the drop down list We will not be using Secure mode for this Appv server so just click next at the connection security mode screen leave the default port type app-v-admins as the Active Directory Security Group name for administrators of the appV server(or just type app-v and click next, then select app-v-admins from the choices available) and enter app-v-users as the Active Directory Security group name for users of the appV server Note: This is the group to which all users must belong for access to Microsoft Application Virtualization-enabled applications. Accept the default content folder and click next and then click install to start installing the application virtualization Management Server if you get Error 25019, go back into SQL management studio and make your appVadmin user a SysAdmin and try again Once setup completes, click Finish and restart the server as requested

have you installed the PSP role on the server that has WDS installed on it ?

can you verify that the SMS Agent Host service is started ?

what do you see on the client when you PXE boot ?

hi all, as the final part of the server update, I will be reinstalling the server hosting the forums over the next few days, I've prepared a mirror server and I'll make a DNS switch sometime during this time period.... If all goes well you won't notice a thing, but just in case something goes wrong I want you to understand why (i've mirrored the site, will point DNS to the mirror, then reinstall the old server, then restore the forums on the server, then point dns back to the original server) my aim is to keep this as invisible and seemless as possible but who knows what may happen cheers

Windows 7 RTM Build 7600.16385 includes a potentially fatal bug that, once triggered, could bring down the entire OS in a matter of seconds: "The bug in question - a massive memory leak involving the chkdsk.exe utility - appears when you attempt to run the program against a secondary (i.e. not the boot partition) hard disk using the "/r" (read and verify all file data) parameter. The problem affects both 32-bit and 64-bit versions of Windows 7 and is classified as a 'showstopper' in that it can cause the OS to crash (Blue Screen of Death) as it runs out of physical memory," reports InfoWorld's Randall Kennedy. Microsoft is claiming the bug is a chipset driver issue, but Kennedy's testing of the latest Intel INF Update Utility driver set and VMware virtualized chipset drivers suggests otherwise. "This is clearly a Microsoft bug - and the fact that it manifests itself via the chkdsk.exe utility makes me wonder if it isn't something intrinsic to the Windows 7 version of the New Technology File System (NTFS) driver stack." Worse still, user comments suggest that Windows Server 2008 R2 suffers from the same flaw. via > http://www.osnews.com/story/21951/Critical_Bug_Could_Derail_Windows_7_Launch

did you use Computer Association to import the computer into SCCM, or is this R2 ?

what does your SMSPXE.log say ?

did you set any dhcp options on the WDS server ? are you absolutely sure you are not prompted to press F12 as part of the pxe process (to gain access to sccm...)

is this a virtual machine ?

first things first what problems exactly ?

you could specify in the custom severity field that it's LOW for example and search for that but then you'd have to do a lot of manual work deciding which updates were 'LOW', however I did a quick test and it seems to work see pic, the update in the pic may require a reboot but I marked the custom severity of it under the All Windows XP Updates search folder as LOW for this test, then created a new search folder as you can see below

hi, please have a read of this post to get a better overview http://www.windows-noob.com/forums/index.php?showtopic=1005 but essentially, you must have wds installed on the sccm server if you want to host the PSP role *pxe service point* on that server or you could host the psp role on another server with wds, for DHCP, the dhcp server can be on another server too but if so you'll have to set dhcp server scope options read the Prerequisites for Installing Configuration Manager on Technet to get the full picture... cheers

did it make a difference ?

on the client open a command prompt and type nslookup then paste the results of that here please

how to prompt for Computername during OSD If you want to be prompted for the computername during a deployment (works for the R2 release of SCCM 2007) try the following on your deployment collection, right click and choose modify collection settings create a new variable called OSDComputerName and leave it blank Advertise your task sequence to this collection, but make sure that the Task Sequence is not set to mandatory now, when the Task Sequence executes it will prompt you for the computername during OSD, cool huh ? click on the variable when you see it and enter your desired computername.. Can I script it ? oh and here's another way from the very talented Michael in Denmark easy way to change PC name during Deployment and here's a script sample Set env = CreateObject("Microsoft.SMS.TSEnvironment") Set SWBemlocator = CreateObject("WbemScripting.SWbemLocator") Set objWMIService = SWBemlocator.ConnectServer(strComputer,"root\CIMV2",UserName,Password) Set colItems = objWMIService.ExecQuery("Select * from Win32_BIOS",,48) For Each objItem in colItems env("OSDComputerName") = objItem.SerialNumber next _________________________ Just run this script after the Deploy OS step. It will set the SCCM variable "OSDComputername" to the serial, and the rest will take care of it self... Related reading:- here's the Technet version of the same

you have to fix this error first sounds to me like you have an authorisation problem, so.... did you configure IIS exactly as specified in the SCCM setup guides here ? including all the WEBDAV parts ?

Edit: just use the following http://www.petervanderwoude.nl/category/USMT-40.aspx you can add /lac to that to append... this is great, well done on figuring it out, i'll be sure to return to this topic when i get the chance to test this, however, microsoft recommend that we DON't edit the mdt files directly, but instead apply changes via other methods... ie: to add additional command lines like /lac we need to customise that via the task sequence i've got that someone on my lab server and will find it and post it here later but that's for this info, it's great !