anyweb

as you posted this here and on Technet, I answered it on technet first http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/d38c66e7-fc2a-4430-aa16-207d19763591 cheers niall

Now that we have created our new Deployment Package lets deploy it ! Expand our Deployment Management node, and select our Windows Vista Service Pack 2 Standalone X86 X64 deployment management task Right click and choose properties, click on the Collection Tab and then click on Browse Pick a Test Collection (which you must create yourself, and which must have some test Vista computers that you want to test this Service pack deployment on) and Click ok click Apply then ok you are now ready with the Deployment. Monitor your Vista Test Clients to verify the Service Pack is deploying... At this point, you must monitor your Vista Test clients to verify the Service Pack is actually deploying you can do this by checking your WUAHANDLER.LOG file, it should show something like the following the (Missing) bit means that the update isn't installed yet, later in the log you'll see

In this guide I will show you one way of Deploying Service packs using your Software Update Point in SCCM. In this example, I will deploy Windows Vista SP2 to our Vista Clients (both 32 bit and 64 bit). In a production environment, always refer to Technet for Best Practise. Create a new deployment package Expand your Software Updates node in ConfigMgr and Run a Syncrhonizaation by right clicking and choose Run Synchronization.. Once it is done, expland your search folders and expand your Windows Vista All Updates search folder. The Windows Vista All Updates search folder criteria are * Product "Windows Vista Ultimate Language Packs" OR "Windows Vista" * Expired No * Superseded No In the Look For drop down menu, type in Service Pack 2 Standalone and click on Find Now, you should see results similar to below. Select all updates found in the search, right click and choose Deploy Software Updates Accept the License Terms give your deployment a name like Windows Vista Service Pack 2 Standalone x86 x64 select our default All Microsoft Updates Deployment Template which we created when we setup the SUP choose to create a new deployment Package give it a suitable name and description such as Windows Vista Service Pack 2 Standaloneand create a new folder for the service pack such as \\WIN-CILZXI45G1Q\patches\Service Packs\Vista\Vistax86x64Sp2 Tip: For package source, you can click on browse, then browse to your chosen server, right click on your patches share, create New Folder, give it a suitable name Select your Distribution Point(s) Select download software updates from the Internet and click next select your language and then set your schedule like this review the progress (might take a while to download the Service Packs) finally after a long wait, your 1.75GB of updates should be downloaded and provisioned

which boot image are you applying the drivers to and can you provide a link for me to the drivers you have tested

setup.exe -ms will install FireFox silently after you rename the firefox setup.exe file no need for any other package maker to do that.. but i see your point, having to update it regularly could be a pain, I would tend to only upgrade apps when a security problem requires it or for functionality reasons, I would suggest you contact the good folks at FireFox and ask them if they can assist with some SCUP implementation cheers

i do, and the forum is closed for now, sorry.

you must keep the blank for staging collection EMPTY at ALL TIMES never put systems in it and never link to other collections in it, ever. you do this because all of your Deployment Management Tasks will point to the 'blank for staging' collection by DEFAULT. That is the way you want it to be, the LAST thing you want to happen is for an untested patch or service pack to go out to all your servers or clients causing mayhem in your organisation keep blank for staging empty Always, and use the phase 1,phase 2, phase 3 and test subcollections to test patches, working your way from test > phase 1 > phase 2 > phase 3 by the time you've reached phase 3 ALL of your systems should be targetted and patched with your selected patches and you then point your Deployment Management tasks back to blank for staging cheers

what do the ccm logs on your client say ? any errors there ?

hi dezdog make sure you are using the windows Vista network drivers for boot.wim see the following post here to find out how to inject the drivers properly into a boot.wim file

nice, now all you have to do is add a © windows-noob.com at the beginning of the PDF cheers

during the install did you add BOTH ASP and ASP.NET, or just one.. ? uploads are working correctly now, fyi

i had to update the forum software to a newer version and it seems stable now, i will keep monitoring it of course... if you have any problems please post them here or drop me a mail uploads are now working again...

first of all I want you to know that I am aware of site problems causing downtime, i don't know what is causing it yet but it seems that the server gets overloaded and dies, I am investigating....

add ASP.NET and please just upload the screenshots here instead of linking to some site that posts a popup advertisement as soon as i click on it

could it be a firewall issue ?

check your PSP role certificate (pxe support point role) http://www.windows-noob.com/forums/uploads/monthly_09_2008/post-1-1222340737.jpg is the date valid or expired ? this is how to set it up

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 ?