anyweb

indeed and it amazes me that there is no logic built it to disallow you from selecting the computers Container, it just lets you do it knowing full well that the ts will fail

hi Eswar, if you press f8 before it gets this far can you browse to c:\ and do you see the folders we need to create like c:\usmtoffline etc ? remember when testing if you fail for whatever reason that you'll have to delete those two usmt folders as i havn't built in any checking into the TS to see if they are there already (in the create folder part...)

good question, the wol feature is used to wake the computers up if they actually need an update targetted in the deployment management task, if they don't need one or more updates they are not woken up, also, once woken up the update(s) are applied and that is all, you'd have to leave them on or package some other solution to power them off again, or wait for R3 which will have several power management features revealed

first of all the firefox guide only shows you how to install an app, if you want to install apps based on active directory security groups then that's another thing altogether and you can do it using a task sequence or via AD groups linked to collections back to the firefox guide, did you get that to work ? is your advertisement Mandatory or optional ? if you want it to appear in the RAP (run advertised programs) make it optional cheers niall

does the WDS service start now ?

is it a Dell, if so you are lucky, you can create a package to enable/disable changes in the bios with a tool called DCCU, if its not a dell then i don't know cheers niall

what result do you get when you try this ? Open a command prompt on your client hardware (the machines you intend to be deploying to....) and type wmic To find out the model name type this CSProduct Get Name The result is what we need

I came across this while building a USB key to do a standalone deployment and the error produced wasn't so helpful so I thought i'd document how to resolve it. Error: Some required packages are not available in selected distribution points. Please select more distribution points. Ok, based on the error I tried to select all dp's but still it failed with the same message, meaning i could not continue with the wizard. So then I started to troubleshoot the problem: I checked all packages referenced in my selected task sequence and all showed up ok in package status and the selected distribution point was indeed listed. I updated each package listed in the Task Sequence References on the respective distribution point. I turned to the internet for answers. After a quick search I found no hits so I set about figuring out what the error really meant. I checked my System Status, Component Status and saw that the Distribution Manager logs (SMS_DISTRIBUTION_MANAGER) were in a critical state, so i selected it and looked at the messages within. There were two errors which caught my attention, Message ID 2302 and 2307. They were telling me that Distribution Manager did not have access to either the package source directory or the distribution point amonst other suggestions. So I set about looking at the Package details using the package ID. That revealed the the package source was missing, my own fault, I removed some wim files to free up space on my HyperV laptop and simply forgot about it. I found the missing wim, replaced it, updated the dp and re-ran the wizard, this time all 6 of 6 packages were seen and I could complete the wizard. so the lessons learned from this are:- * make sure not to delete something unless you know it won't be used again * when creating standalone media, make sure X of X packages matches, if it's X-1 of X, or another variant of that then it won't work cheers niall

i have a feeling that C:\Program Files (x86)\Windows Imaging\wimgapi.dll 6.0.6001.18000 might be causing the failure, see if you can replace it with the other version or just delete it and try again

maybe the firewall on your server is blocking the communication ?

cool, can you confirm what you changed in that file (paste it here please)

windows 7 machine can be sysprepped of course, as sysprep is built into the os now (since vista)

yup, they have renamed the task from import microsoft .... to Create Microsoft Deployment Task Sequence, perhaps to make it clearer, so go ahead and select that option, i'll update the documentation [done] thanks for bringing it to my attention

can you try this please http://www.windows-noob.com/forums/index.php?showtopic=669 cheers niall

give everyone full access as a test just to rule out ntfs and share permissions

what are the share permissions on the SMP folder itself, perhaps they are too restrictive ?

hi anndc, can you post some of the messages you are seeing please ?

no, just change your logic, DO all bits in this group if model = DELL whatever otherwise it will skip that group

Overview: The following scenarios are used to show the end-to-end process of creating, publishing and delivering a virtual application: * Sequence * Publish * Deliver a Virtual Application using the App-V Full Infrastructure Download the Manual (PDF) Try the lab for yourself here

if both of you search for all copies of wimgapi.dll on your systems and report back the versions and file locations of that file here please

ok you have wds on one server right ? can you install the PSP role on that server yes/no ?

this is how create a new group for each model and place the appropriate software install commands in each group, cheers niall

try temporarily disbaling the firewall on the client and do a Data Discovery, do you see the client in configmgr collections ? is it approved and client=yes ?

i assume you mean that the video driver is not appearing once xp is installed or ?

it shouldn't hang, verify that there isnt a UAC prompt or some other process holding it back (anti-virus perhaps ?)