anyweb

where are you planning on installing the client ? i'm not following your train of thought exactly... you can't install the client from the CAS because it doesn't manage clients, you can only install it from your primary sites.

that link doesn't work

thanks !

are all of your fujitsu's doing the exact same thing ? tried a bios update ? tried a network driver update ?

try this link

try with a different hardware vendor and note the differences, my experiences with WOL are with Dell Hardware only. NIC's asics (the hardware brain of a nic that deals with wol and other things) is frequently updated via a Bios upgrade...

that's bizzare and exactly as you say it's the opposite of what i'd expect is normal behaviour, but it could be bios version related and/or network driver related what hardware are you using ? (manufacturer)

ok probably bad wording from me then, i'm aware of the dirty bit that's set on a disc if the system is shutdown improperly, and perhaps they are related but from my understanding (and you can test this on real hardware) a 'bit' is set on the nic (network card) to flag if there's been a dirty shutdown or not (at least it was the case on Dell's), try this simple test, power up a computer, shut it down cleaninly, try wol, does it work ? (just send a magic packet) if it works then power off the same computer by pulling the power while it is in Windows (dirty shutdown) and then try doing a WOL, will it work, most likely not, that's all my point is, and i'm wondering if that is the issue you are seeing

well my understanding with WOL is that theres a dirty bit involved, ie: with a dirty shutdown (power off without proper shutdown) the bit is set and WOL won't work until the computer is booted up and shutdown properly this could be part of your problem, have you looked into that ?

hi, this is indeed a good question, i'm investigating this for you and will come back as soon as I can

i'd go for option number 1. always. maybe someone else has another idea

then it uses USMT4 and i'm sure the same rules will apply

can you clarify this please are you saying that you are not distributing ALL packages referenced in the task sequence to all dps ? what if (for example) you have a Danish user in Sweden who needs their computer reinstalled, are they out of luck because they are not in Denmark ?, my point being, i would be distributing all referenced packages in a ts to all dps..

as i replied on the technet forums your versions are out of date, get RC2 for configmgr 2012 and RC1 for MDT and read the release notes chm file for MDT 2012 RC1 cheers niall

you use antimalware policies to do that, you can Import predefined policies by clicking on Import in the ribbon, and there are many predefined policies there which exclude specific services/files/folders etc depending on server role, browse through them and you'll see what I mean.

how did you capture the wim file ?

are you migrating from Windows XP to Windows XP or Windows XP to Windows 7 ? please confirm

you must take this one step at a time, the red arrow in your screenshot is indeed important, you can verify this by pressing F8 during deployment and checking ipconfig to see that you are getting a valid ip and that you can ping the FQDN of your configmgr server. if no network card is found then you need to add network drivers for the hardware you are deploying on has the user you use to join the domain been given the correct rights to join computers to the domain, check c:\windows\debug\netsetup.log for domain join failures., also it's best to post logs etc here in the forum post so others can join in, I get many mails from people asking for help and i don't always have time to respond to them all

hi there Magnus have you seen the following on Technet ? from here - http://technet.microsoft.com/en-us/library/hh696543.aspx

Last week, Microsoft cut the number of Windows and Office product keys it includes for TechNet subscribers. Readers tell me that doesn’t matter, because every key is good for multiple activations. But is that really true? My investigation says yes, although exact details are murky. Over the years, I have written tens of thousands of words about the mysterious workings of Microsoft’s Windows activation technology in XP, Vista, and Windows 7. It might be one of the most arcane and misunderstood technologies of the PC era. Last week, the topic came up again when I published details about Microsoft’s decision to cut the number of Windows and Office product keys it includes with TechNet subscriptions. (See “Microsoft slashes product key allowances for TechNet subscribers.”) Two years ago, a TechNet subscription included 10 product keys for each version of Windows and Office. That number was cut to five in late 2010, and to three earlier this month. A half-dozen readers left Talkback comments and sent emails telling me that it’s “well known” that each TechNet product key can be activated 10 times. Several quoted Paul Thurrott, who wrote in 2010, without citing a source, “Each product key can be used to install up to 10 versions of the OS or application, for the most part.” So, they say, no big deal—three product keys equals 30 installations per Windows and Office version. But is that true? I’ve fact-checked this issue several times over the years and have never been able to track down a definitive answer. This policy is not documented on any official Microsoft site. I have found unofficial statements on Microsoft’s public support forums and in private emails, like this example from a front-line tech on a support forum: You have 2 product keys for most products, and for Windows Retail keys, each of these keys will let you activate at least 10 times (it depends on the key type). Another customer got this message from a support rep last week, via email: Smoking gun? Well, I’m always suspicious of information that comes from front-line support reps, who often are well meaning but not fully in the loop. In addition, these two messages are actually contradictory. One says each key is worth at least 10 activations, the other says up to 10. Is either statement true? If so which is it? I asked a few official and unofficial sources at Microsoft. It took 48 hours and much hemming and hawing, but I finally got a Microsoft spokesperson to confirm that 10 activations per subscription key “is not the official policy across all products.” She went on to note that “different products call for different activation parameters.” That’s something more than a non-denial denial, but it’s still far from clear. And that, as it turns out, is the crux of the problem. The official policy for retail Windows product keys is that you are allowed one activation, with an unlimited number of reactivations on hardware that is substantially the same as the system on which the OS was originally installed. But the activation servers, which do the grunt work of processing activations over the Internet, aren’t so rigid. There are, in fact, business rules designed to flag unusual behavior and allow or block activations based on those rules. For example, if you activate a retail copy of Windows on a PC and then, 18 months later, try to activate that same key on a different PC, your activation will probably complete without error. Why? Because that’s the behavior of an enthusiast getting a new PC, not a pirate. If, on the other hand, the same key is used to try to activate Windows on six different PCs in widely scattered geographical locations over a short period, that key is likely to be flagged as stolen. Microsoft doesn’t like to go into detail about those business rules, because doing so makes it easier for pirates to figure out how to game the system. Crooks who have to guess about how the system works are more likely to screw up and get caught. In the case of TechNet keys, there isn’t a literal 10-activations-per-key algorithm on the activation servers. Instead, the business rules are set to recognize the way that TechNet subscribers—who are typically enthusiasts and IT pros—are likely to use those licenses. They play with it, reinstall on multiple hardware configurations to test compatibility, and try to see if it breaks things. The upshot is that those TechNet subscribers behave far differently from typical retail customers. As a result, the business rules flag TechNet keys as special. They are indeed able to qualify for more activations than an equivalent retail key would get. And if your legitimately obtained keys fail to activate, you should be able to resolve the issue with a phone call or email to Microsoft support. Sources at Microsoft adamantly refused to talk on or off the record about specific numbers used as activation guidelines. But they did confirm that the rules are relaxed: My experience with TechNet downloads and product keys over the years bears that out. I keep good records about which keys are used where, and I can’t remember ever being denied activation because a key had been used too many times. The lack of transparency in the process is frustrating, but it’s also understandable. Software pirates have proven, time and again, that they’re willing to treat each unique key as an asset that can be resold against the TechNet terms of service. Reducing the number of keys in a subscription means there are fewer of those assets to bootleg. As long as legitimate subscribers find a relaxed and tolerant attitude when activation time comes around, this might turn out to be a non-issue. In the wake of the TechNet product key reduction, I’m interested in hearing firsthand reports about your experience with Microsoft’s activation servers. If you’ve had recent experience that can help make sense of how this activation works, please send me an email or leave a comment below. via > http://www.zdnet.com...h-results-river

great stuff ! good job

you can capture an image using capture media then, the following guide is for Configuration Manager 2012 but the main concepts are unchanged - have a look and see does it help you http://www.windows-noob.com/forums/index.php?/topic/5070-how-can-i-capture-an-image-using-capture-media-in-configmgr-2012/ the "0x00000032" error means unsupported, ie: you are trying to do something that should be done in windows PE or vice versa... "0x80004005" error usually means 'access denied' so check permissions. cheers niall

hi Lucie have you checked if the computer you are trying to build and capture has a readable C:\ drive ? press F8 and see can you browse C:\ if not use diskpart to partition it like so diskpart select disk 0 clean create partition primary select partition 1 active format fs=ntfs quick assign once done, try pxe booting again, does it work ? as regards the media player shortcut, anything like that can be removed via separate steps in your Deploy Task Sequence, for more details of build and capture versus Deploy please look at this powerpoint I did and look at the slide notes.

is there any switch in between your configmgr server and the computer above ?

are you using ConfigMgr Beta 2 or Release Candidate 2 ?