anyweb

are you sure thats the log file, doesnt look anything like a normal log file to me, please doublecheck and try again

great stuff thanks for sharing !

When using the "Capture Network Settings" task in a Configuration Manager 2007 (SCCM 2007) OSD Task Sequence on a PC that has teamed NICs, not all of the settings of the NIC may be captured properly. This mainly applies to DNS and WINS settings that are set statically. In these cases the settings are not captured and instead are set to obtain from DHCP when the network settings are restored via the "Apply Network Settings" task. http://blogs.technet.com/configurationmgr/archive/2009/11/30/the-capture-network-settings-task-in-a-configmgr-2007-osd-task-sequence-may-not-properly-capture-dns-wins-settings-on-teamed-nics.aspx

we can try this evening when i have time, contact me via msn.

no it can't you must enter the computername and MAC address or computername and GUID cheers niall

what custom settings are you trying to set exactly ?

Microsoft's latest round of security patches appears to be causing some PCs to seize up and display a black screen, rending the computer useless. The problem affects Microsoft products including Windows 7, Vista and XP operating systems, said Mel Morris , the CEO and CTO for the U.K. security company Prevx. Prevx was alerted to the problem by users of its security software last week, Morris said. Microsoft apparently made changes to the Access Control List (ACL), a list of permissions for a logged-on user. The ACL interacts with registry keys, creating visible desktop features such as a sidebar. However, the latest patches appear to make some changes to those registry keys. The effect is that some installed applications aren't aware of the changes and don't run properly, causing a black screen, Morris said. However, the latest patches appear to make some changes to those registry keys. The effect is that some installed applications aren't aware of the changes and don't run properly, causing a black screen, Morris said. Security applications seem to be particularly affected. Morris said users of other security products have also complained about the issue, even going so far as trying to reinstall the operating system to fix it. "If you've got this problem, it's massively debilitating," Morris said. Prevx has released software that fixes the registry to match the ACL settings, which should resolve the problem, Morris said. Users could do this on their own by modifying their registry settings, but making alterations to those settings is risky since it can severely affect how the operating system runs. full story > http://www.computerworld.com/s/article/9141568/Latest_Microsoft_patches_cause_black_screen_of_death

I havent tried it with R2 yet but Peter claims it works ok, did you triple check your webdav settings ?

if you want a computer to get an advertisement then that computer must be in a collection that the advertisement is advertised to if it isnt in that collection then you need to find out how that collection is gettings computers inside it, it can be in a variety of ways including direct membership or a query to place computers into the collection based on active directory security group membership in it's easiest form you could just create a direct membership for a computer to add it to a collection, or simply install right click tools and add the computer that way

do you mean that you want to change the site code on a client, or something else ?

what does this log tell us C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log

how big are the files ?

here's a deep dive from Jannes aLink about what to expect in R3 http://www.jannesalink.com/blog1.php/2009/11/26/let-s-dive-deeper-in-configmgr-r3 cheers niall

looks like its seeing your windows deployment services server and not the pxe boot from sccm. check your psp role settings on the sccm server...

can you take a photo/screenshot of what you are seeing

so before it restarts stop it with F8 and copy the log to a network share

you'll have to configure the application to not look for updates prior to making a package out of it and distributing that package.

is webdav configured like so ? http://www.windows-noob.com/forums/index.php?/topic/490-how-can-i-configure-sccm-2007-sp1-in-windows-server-2008/

you have to create the MST file yourself using ORK.EXE (the office 2003 resource kit) some info about how to do that here > http://www.supinfo-projects.com/en/2005/mst_o2k3_uk/1/

Push the client to Targetted Collections In this example we will push an installation of the client to the All Systems collection, this is in a Lab so this is ok. In a production environment you will want to test this on small groups first and work your way up. Right click on the All Systems collection and choose Install Client set your options making sure that Always Install is selected click Finish when done to verify the installation of the new client is happening, on the clients open task manager and look for ccmsetup.exe after some time you can verify the client version on the client As the client starts getting installed, the report we used in the beginning will show the new numbers increasing

Distribute the Client Package to your Distribution Points If you want to install the latest version of your Client in Operating System Deployments then you'll need the client package from definition updated to your Distribution Points. Expand the client package you just created, click on Distribution Points. Choose New Distribution Points. when the wizard appears click next select your distribution points for the client click next and then close when done.

Create a New Client from Definition Package One of the steps when deploying Operating Systems involves installation of the Configuration Manager Client (Setup Windows and ConfigMgr Step), as a result we want our Client Package files updated to the new version, so If you have not already done so you need to create a client from Definition package. (If you already have a Client Package from definition, simply update that to it's distribution points and you'll be fine.) Expand Software Distribution and right click on it, choose New, Package From Definition click Next when the create package from definition wizard appears choose configuration manager client upgrade and next choose always obtain files from a source directory and click next choose Network Path (UNC Name) and specify the directory containing the source files for this package as \\SERVERNAME\SMS_XXX\Client where SERVERNAME is your SCCM server, SMS_xxx is SMS_ and your site code (eg: SMS_WDN) click Finish at the summary screen

This is one way of updating your SCCM ConfigMgr Client after an upgrade. There are more ways of doing this. This guide is done in a Lab Environment. Please refer to Technet for recommended practise. After you have updated ConfigMgr from Sp1 to Sp2 you will have all your configmgr clients still running the old version of ConfigMgr (Sp1). Identify Client Versions To find out how many are using the old client you can use a built in report called Count SMS Client Versions, right click on the report and choose Run. the report will show you how many clients you have running the old (sp1) client, and if any, how many are running the newer sp2 client. so in this Lab I have 13 clients that need to be updated to the newer client version.

have you tried reading the manual for the switch, sorry but it's not my area at all

I've updated the post to include the download details here