anyweb

hi Jb can you post the solution to this please, it was one of the posts lost in the forum upgrade today cheers

Step 5. Target the Deploy Task to the collection you want to receive the updates Expand the Deployment Management Tasks node and right click, choose Refresh you will see that the task is targetted to the Blank for Staging collection which is an Empty collection, right click it the Deployment Management task and choose properties select your targetted XP collection click ok and apply Step 6. Monitor your XP machines and verify that they are receiving the Updates just before the deadline occurs, your XP machines should start receiving the new Update Policy and inform you finally, once the deadline has been reached the updates are installed automatically

Step 4. Deploy the selected updates right click the selected updates again and this time choose Deploy software updates give the Deployment Task a name for Deployment Template, choose the one that suits your environment select our Deployment Package go with the Default Choice of Download Software updates from the Internet select your language set the Schedule as below review the summary and close

Step 3. Using the Search folder, select the new updates Open our Windows XP All Updates search folder and sort by BulletinID as you can see there are a few updates released since our Deployment Package was last updated a month ago, and we need to select those new updates since MS09-026 which was the last update listed in our Deploymet Package (From June 2009) Right-click and choose Download Software Updates on the select a deployment package screen click on browse and select our All Windows XP Updates Deployment Package on the Download Location screen choose to download software updates from the internet select your chosen language and click Finish click next and close when prompted...

ok the new look is now here, so............... what do you think ?????

hi all, back in June 1st, I notified you all that the site would be changing look soon, and today I undertook that job. For those of you that are nostalgic here's a quick look at how it was so by now you've probably noticed that the forums look different, yup, they've been updated to the latest release of IPB software today, during the upgrade process I had some mysql issues and dropped the database, the side effect of that was that any posts in the last day or so and any new signups will have been removed, for that I apologise and hope you understand that this is a one man show pretty much, anyway, I've fixed the database issues (it was a mysql user GRANT issue, missing some permissions) and all seems good, still to do 1. get the portal working again (or the Front Page to you and me) 2. get windows-noob.com LOGO, VOLUNTEERS anyone ??? 3. verify posting works etc... i hope you will all like the change and enjoy the benefits it provides cheers niall

no it has nothing to do with the PXE filter for MDT, can you please check your System Status component logs in SCCM to see if there are any obvious problems, other than that are you creating the boot images as outlined in the Deploy Vista guide here ?

were there some errors in System Status component logs to alert you of the fact that your management point was broken ?

Introduction In this guide I will show you one way of updating your monthly updates released from Microsoft on the second Tuesday of every Month. Many different scenarios can be followed to deploy software updates. In this example, we will use a Software Updates Deployment Package called All Windows XP Updates to store the updates we want made available to our XP machines. We will create a new Deployment Management Task to deploy the new updates, and we will clean up our previous Deployment Management Tasks and remove any expired updates referenced in it by deleting them. As we are not using Update Lists in this guide we will not be concerned with reporting, but if you want to report on the status of your Updates, you should use Update Lists as Part of your Process. This Deployment Package had been created earlier when setting up the Software Update Point, but you can create a new one if you need to. We will use a Deployment Management task to start the deployment called All XP Updates. and as you can see from the screenshot above it contains some updates which are expired and this is noticeable because of the Grey Icon. We will also use our Windows XP All Updates search folder which is created with the following Search Folder Criteria Step 1. Run a Synchronisation. Expand your Software Updates node in configmgr, right click on Update Repository and choose Run Synchronisation. Answer Yes when prompted. You can verify that the synchronisation process has completed in the Site Status, Component Status, SMS_WSUS_SYNC_MANAGER log. Look for Message ID 6702 which is SMS WSUS Synchronization Done. Step 2. Check our Deployment Package To start off the monthly update process we need to first see what updates we currently have in our Deployment Package and remove any expired or superseded updates contained within. Expand your Software Updates node in configmgr, expand the Deployment Packages node and highlight the All Windows XP Updates Deployment Package. Expand the Software Updates node within so that you can see what updates we have, click on the Bulletin ID heading to sort our updates. Take note of the Expired or Superseded updates and highlight them and once done right click and choose Delete. You can press CTRL while selecting these updates and don't forget to scroll so you see all updates. We only want Green updates in our Deployment Package. Click ok when prompted about the Delete process click ok if prompted about Deployment can fail process, this is ok as we will be updating the Deployment Management Task. At this point we now have removed all the expired updates so only green 'good' updates are left, sort the updates by BulletinID again and take note of the most recent one, in our case that is MS09-026

is the firewall disabled on the xp client ? is the timezone the same as the server ? open task manager on the client, click 'show processes from all users' and then push the client out, do you then see ccmsetup.exe start ? remember that the client push installation account must have local administrative permissions on the client so for testing in a lab, a domain admin account would be good

cool, but please do test out application installation via RAP in SCCM

you could virtualise is just for the scrrenshots using vmware, hyperv, xen or whatever or you could use a good mobile phone

no you don't need WINS and have you checked one other thing Timezone ! make sure your timezone on the client pc's matches your server

can you change your vmware BUS to LSILogic instead ?

you could deploy software using a task sequence separately sure, that way you could use Groups within the task sequence to detect various things, like isLaptop or isDesktop or whatever and based upon the detection, install certain software... instead of using Allusers=2 can you please try AllUsers=1 and see what happens ?

WSUS has a known bug in relation to SCCM, in that if it's installed on the same server that SCCM is running on, it can sometimes uninstall itself, maybe that was your problem ?

Step 3. Publish this site in Active Directory Domain Services Note: In Configuration Manager, Verify that the following setting is set Highlight your SCCM Site right click, choose properties, Advanced. For specify settings for publishing and secure key exchange make sure to Select publish this site in active directory domain services Next step > SCCM 2007 SP1 configuration guide - Part 3 The guide covers:- Configuring the Client Agents, setting up client installation methods and configuring discovery methods.

don't reuse the same site code unless you absolutely have to...

add me on msn and i'll take a look if i have time anyweb AT hotmail DOT com

i think you are referring to this followed by this bit update distribution points on a schedule the important bit here is to set this to some value that suits your environment, once a week, once a month, whatever suits you, and.. when you get a new release of Firefox, let's say Firefox 3.0.9 you simply rename it toFirefox.exe and copy it to the Source path listed above, sccm will copy that on the pre-defined schedule and you'll have a new version of Firefox available does that help ?

ok then you are doing something wrong. how have you set it up and what is your setup like ? what user are you logged in to the server as and what permissions does that user have in SCCM

try logging on to that server with an account that has local administrative permissions on the server see here ...

are you only deploying Office 2003 using a Task Sequence, or are you deploying XPsp3 with office as part of the installation, if it is the latter then at what part of the installation are you installing office

ok well my suggestion to you is to test the theory out in a lab environment first, and see for yourself how it works or could work in your environment, then based on the results of that move forward

ok well this error is quite common, you just need to find out what those DDR's are now... so what systems are your logs referring to ?