anyweb

which account are you using to do the actual Client Install, it is specified in the Site Settings, Client Installation Methods, client Push Installation, Accounts it is that user that must be a local administrator of the target machine you want to install the client on

is this in a virtual environment ? have you checked your SMSTS.log ?

What is the Dell Deployment Pack? The Dell Deployment Pack (DDP) is an easy-to-use graphical user interface (GUI)-based tool that integrates directly into the Microsoft® System Center Configuration Manager (SCCM) 2007 (ConfigMgr) console. It eliminates the need for command-line tools and scripts normally used in the Dell™ OpenMange™ Deployment Toolkit (DTK) software. To configure and deploy your Dell systems, you need to select configuration options and commands on the GUI using drop-down lists and check boxes (see "Using The Dell Deployment Pack"). These selections make your system deployment an easy, automated task. http://www.delltechcenter.com/page/Dell+De...ver+Deployment)? Overview of Dell Deployment Pack Features Using the ConfigMgr Task Sequence Editor, you can do the following with the Dell Deployment Pack: * Configure your system's Baseboard Management Controller (BMC), Dell Remote Access Controller (DRAC), Redundant Array of Independent Disks (RAID), and BIOS. You can configure BIOS and RAID using .ini files. You can configure your system settings using the GUI or command-line interface (CLI) options. You can also configure RAID using the Array Builder wizard. * Create a Dell-specific boot image that will be used in the OS deployment. * Create and apply driver installation packages for specific Dell systems. System Requirements: * Microsoft System Center Configuration Manager with Service Pack 1 or newer * At least 1 GB of free disk space on the same drive that contains the ConfigMgr installation files * A configured Network Access Account for ConfigMgr site(s). Supported Hardware Systems The Dell Deployment Pack 1.0 supports the following Dell PowerEdge™ systems: PowerEdge 800, 830, 840, 850, 860, 1850, 1855, 2800, 2850, 6800, 6850, 1900, 1950, 1955, 2900, 2970, 6950, SC1435, 2950, T105, R200, R900, R805, M600, M605, T605, R300, T300, R805, PV0100, PV0500, PV0600, NX1950, M805, M905, and R905. Supported Operating Systems * Microsoft Windows Server® 2003, Small Business Server (SP2, R2) * Microsoft Windows Server 2003 x86, x86_64 Edition SP2 and SP2 R2 * Microsoft Windows Server 2008 Standard and Enterprise Editions (x86) and (x86_64) * Microsoft Windows® Small Business Server 2008 x64 (64 bit Edition) * Microsoft Windows Essential Business Server 2008 x64 (64 bit Edition) sounds cool, now if I can just persuade Dell to send me a Server to test this on.... cheers anyweb

yup, it's either one or the other, or separate them using subnets and networking. cheers anyweb

I had this problem recently and the fix was quite easy, but finding out why it was failing (to install any updates on any machine connected to the SCCM SUP) was difficult. the basic errors in the WUAHANDLER.LOG file found on the client were repeated again and again I googled the Scan failed with error = 0x80072efd. error and got some ideas that it was a lack of commuinication between the client and the sccm sup. This turned out to be correct in the end. The SUP was a WSUS server running as a site server and was multihomed, one network card served the internal network and the other served the public. The SCCM server was on the internal network and tried to access the WSUS but got an error After much troubleshooting i decided to ping the Configuration Manager wsus server from a working machine, it reported the correct IP on the internal network. I then checked a non working client and pinged Configuration Manager wsus server from it, it replied back with the IP address of the WSUS public ip. That was the Eureka moment ~! As a quick test, and configuring IIS on the WSUS server to 'Listen To all IPs' the WSUS server was responding with the correct IP address when pinged, and windows updates started flowing hopefully this may help someone in the same situation cheers anyweb

your WDS service can exist on the sccm server or elsewhere the choice is yours, you can also upgrade a RIS service to WDS, if its windows 2003 server sp1, simply upgrade to sp2 and the ris service will become wds... please review this Technet page about WDS and SCCM cheers anyweb

welcome and thanks for your kind words :-) can you attach your SMS_MP_CONTROL_MANAGER log here please so that I can take a look at it ?

if you notice the WMI query takes place in a GROUP, and the reason for that is it 'asks' the machine what it is, and if it matches what we expect it to be, then and only then does it do all the individual STEPS within that group (quickset and whatever else you add), so if it is NOT a D430 then it will not install anything within the D430 group and it will skip the group completely and go to the next step in the task sequence. I wouldn't mix operating systems types within a task sequence, that's just asking for trouble, it's probably possible but i wouldn't do it that way i hope this helps cheers anyweb

ok then, try and catch me when i'm online and we'll do a session, my email is anyweb AT hotmail DOT com

are you willing to let me do a remote desktop to the server and look at it ?

ok so are you saying that the client software is not getting installed or that it just says 'client=no' in your collections ? is the client computer in your boundary ???

did you check your firewall settings on the client ? disable them for testing purposes the client push install account MUST BE A MEMBER of the LOCAL ADMINISTRATORS group just for the client installation, after it's installed you can remove the account from local admins group if it isnt, it will never install verify both those things cheers anyweb

ok then, continue with the REST of the guide and ignore that problem for now. We'll come back to it later but i'm sure you have a configuration issue somewhere.. if you are willing I can do a remote desktop session with you but for now, for any new problems you get please open a NEW topic/thread cheers anyweb

The Windows 7 beta release is already a few months old now, and Microsoft has already made quite a number of changes to its new windows release after that, as detailed in the Engineering 7 weblog. These changes would make it to the public via the release candidate, but it has always been a bit unclear as to when it would arrive. Thanks to a slip-up, we now know the RC is coming in May. via > http://www.osnews.com/story/21204/Windows_...e_Coming_in_May

if it says 'client=no' then a Discovery Data Cycle hasnt been run yet, try running it manually by initiating the action on the client, then do a refresh in ConfigMgr cheers anyweb

delete your X86 bootimage package and recreate it, then distribute it, then update the DP's then try again, cheers anyweb

are the servers raid ? can you not do a low level format on the hard discs which should erase any/all boot records for ever and then do a new deployment on them ?

try this net use * http://127.0.0.1/ does that work ?

is iis installed on this server or another one ? what type of USER are you doing this as ? can you copy and paste the EXACT commands you are typing and the output here please cheers

ok then, is your server an all in one ? ie, is DNS, DHCP and AD all installed on it ? i need more info...

what type of hardware do you have on this box with boot problems ?

is your firewall disabled or enabled ? have you left out any steps at all ?

post your new smsts.log file and i'll look at it to see whats wrong now cheers anyweb

adding the 64bit boot image would not break the WDS service, so you'll need to find out whats wrong with that (read the event viewer..) have you tried a server reboot ?

you have to fix this then find out what package that is (CRO00001:11) and re-distribute it...