anyweb

you need to verify that you have created a Distribution point for the package, then update the DP for that package, if its a boot image then it should be also distributed to the PXE share....

Builds for Windows 7 keep powering forward; it seems there are new ones being reported weekly, but here's one that might be worth sitting up and paying attention for: it appears Windows 7 has reached build 7105, an RC build. But in addition to this, it's worth remembering that a Windows 7 RC could possibly be available April 10th. This timing makes it seem as though Neowin's exclusive source was dead on, and that in a few days time Microsoft will announce availability of an RC build for its latest operating system. The string for this build is 6.1.7105.0.090404-1235_x86fre_client_en-us_Retail_Ultimate-GB1CULFRER_EN_DVD, and it was compiled on April 4th. Many contested that this means it's a fake; April 4th is a Saturday, but those thoughts have been dismissed with the fact that Microsoft still compiles builds on Saturdays. Russian site DJForum.ru is reporting this... more info > http://www.neowin.net/news/main/09/04/06/w...-escrow-reached

This guide assumes you've installed a SUP within SCCM and configured it for software updates to your clients. You may notice that the familiar windows update icon still appears even though SCCM is handling windows updates to your client. to resolve open up Group Policy Management and right click on the Default Domain Policy, choose Edit. expand Computer Configuration\Policies\Administrative Templates\Windows Components and then select Windows Update from the list *scroll down* find the setting configure automatic updates right click it, choose properties and then set it to Disabled The Windows Update Icon will disappear however you will still receive updates from Configuration Manager as normal. to speed up clients getting this GPO open a command prompt and do gpudpate /force cheers anyweb

the way you can 'backup' an existing partition or drive within Vista deployment is by utilising USMT (user state migration tool) that's the supported way, but it's by no means easy more info on USMT here > http://www.windows-noob.com/forums/index.php?showtopic=231 you could possibly script it yourself but if it's only for one pc then why bother, or is this for more than one ? if so, USMT is the answer.. cheers anyweb

install the desktop experience feature, and it should resolve.

hi, sorry i missed that, can you try to right click on a user listed in All Users and choose Distribute Software, and go through the wizard, after selecting the Program you'll get the chance to target the advertisement at the collection the user is in or create a new collection with that user in it... try creating a collection with the user in it via this wizard... does this help in any way ? ie: does anything get targetted to that user ?

Thanks to Windows Server boss Bill Laing, we now know that Windows Server 2008 R2 will be released this calendar year. Since Windows Server 2008 R2 is the server version of Windows 7, we can deduce from this announcement that the successor to Windows Vista will certainly arrive before the end of the year. And what's up with the "quite major announcements" about Windows 7 Microsoft is talking about? Bill Laing revealed the plans for 2008 Server R2 during an interview. Generally, the server versions of new Windows releases are shipped later than the desktop variants, because the former needs more rigorous testing. As such, it's pretty much certain now that Windows 7 will arrive before Christmas, and Microsoft may even try to pick a few back to school sales by releasing in October. And that brings us to another interesting piece of news, coming from the British PC Pro magazine. According to Microsoft's Windows OEM manager, Laurence Painell, the company has some "quite major announcements" up its sleeve for the coming weeks to coincide with the release of the release candidate of Windows 7. There's no specific release date set yet for the RC, but a recent "accidental" leak indicates the RC will most likely arrive somewhere in May. via > http://www.osnews.com/story/21252/Windows_...eased_This_Year

the first things to check are that the computer in question is listed as Client = Yes in the All Systems collection, is it ? and that it's Approved...

you must fix the AD issue first by following this guide to Extend the AD schema for SCCM http://www.windows-noob.com/forums/index.php?showtopic=488 please go through it again and see did you miss any step and verify that the account you are trying to extend AD with is a member of the Schema admin security group once you fix that we can look at your other errors

Please note that all screenshots below here are what your systems will see on first boot after being deployed with the captured WIM we have just created above. after the computer restarts you'll get the chance to see your sysprep settings... after a few more screens and one last reboot you'll get to play with your XP SP3 client, if you are left with some drivers not installing correctly then take a look at this post. Now all you have to do is deploy the image by creating One more task sequence, this time the task sequence will use the Captured XP sp3 image as the operating system image. If you find the SCCM client is not installed after deploying this image then read this post cheers anyweb

have you tried network discovery, that can be used to detect things that are not picked up using AD discovery, it does add additional network traffic though... cheers anyweb

thanks for the link, and you are right, that is for basic authentication, I'll add that to my documentation cheers anyweb

The MDT Solution Pack 1.0 used to be Microsoft internal tools only, but they made v1.0 available from the Business & Industry section of microsoft.com. So what is the MDT Solution Pack 1.0? The MDT Solution Pack extends MDT 2008 (Lite Touch) with a lot of goodies, for example: - Readymade scripts for deploying 40+ common apps (from Adobe, Microsoft, Sun etc.) - Readymade Task Sequences with 50+ common tweaks (scripts) for XP, Vista, 2003 and 2008 - Additional sample rules (customsettings.ini) - Updated/Extended Wizards - Additional docs & Tools Link to the MDT Solution Pack (v1.0) download and other info http://www.microsoft.com/industry/healthca...esktop/mdt.aspx Note: The MDT Solution Pack 1.0 is provided AS IS and is not supported by Microsoft.

it's probably the ConfigMgr client installation files, make sure to redistribute the package to it's DP's the package in question is this one http://www.windows-noob.com/forums/index.p...dpost&p=713 please note, you can verify a package from its package ID and by looking under System Status/Package status....

hi Dom, i'd need to see the whole smsts.log to determine the failure, can you provide me with that please ?

that is totally weird, on all the server 2008's i setup with SCCM i've never enabled that feature, I hope to get a definitive answer to this problem soon.

yes it will work with 2003, just post any problems you have here when they happen good luck cheers anyweb

look at this so, find out what package SPH00003:1 is, and verify that it is distributed properly to DP(s) then try again cheers anyweb

you'll need to review your SMSTS.log file to find out why read this post for details of that http://www.windows-noob.com/forums/index.php?showtopic=546

you can get the MAC address by simply pinging the computer and then arp'ing it eg: U:\>ping xp1002 Pinging xp1002.windows-noob.com [94.75.228.161] with 32 bytes of data: Reply from 94.75.228.161: bytes=32 time<1ms TTL=128 Reply from 94.75.228.161: bytes=32 time<1ms TTL=128 Reply from 94.75.228.161: bytes=32 time<1ms TTL=128 Reply from 94.75.228.161: bytes=32 time<1ms TTL=128 Ping statistics for 94.75.228.161: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms U:\>arp -a Interface: 94.75.228.161 --- 0x2 Internet Address Physical Address Type 94.75.228.161 00-23-ae-00-62-d7 dynamic so now you have the MAC address ( 00-23-ae-00-62-d7 ) of the computer and you already know its computername.... does that help ?

ah ok <04-01-2009 15:57:03> Machine is running Windows 2003 SP1 or later. (NTVersion=0X600, ServicePack=1) through me off, what type of user permissions are you using to do this ? is the user a local administrator of this server ? have you tried uninstalling WDS, reboot, delete any folders/shares setup from wds, reinstall wds, and then try again ?

more and more people are coming here to get answers to their SCCM and Windows Deployment problems, how did you end up here ? vote and tell us ! cheers anyweb

then you should choose All Windows XP updates and let the windows update process install all that it can during deployment, i know you can block ie7 being installed, more info here and here's one for blocking IE8, so if you enabled both i guess you'd be left with IE6 You can at any time select updates in your Search folders after doing a Run Synchronisation, right click on the ones you want and choose Deploy, doing so will allow you to create a New Deployment Management task, or to update an existing one, you can REMOVE any updates that you DON'T WANT to be advertised to your clients by selecting it from your Updates Deployment Package and deleting it look at the screenshot below to understand how easy that is over time you can sort your Enterprise searchs like I have here, obviously you should customise this to suit your environment.. the above search folder criteria are as follows

good tip, thanks½!

is this server 2003 sp1 or sp2 ?