anyweb

sounds like a nice project, any data migration involved ? all you need to do in the simplest form is to create a Deploy Windows 7 collection and advertise your task sequence to it, you can import computers using a file (excel csv file) or you can advertise the task sequence to all computers (not all systems but say, all Windows Vista computers) but hide it from RAP (so users dont see the advertisement) by stipulating a different OS to the one you are running in your company (ie: limit the advertisement to Windows XP X64 assuming you have none of them...) this means none of your vista machines will see the advertisement until then PXE boot (network boot) and then they can select the task sequence and migrate as normal you can get details of that and password protection of the task sequence here: How can I password Protect a Task Sequence ? Password Protecting a Task Sequence if you want to advertise multiple task sequences with a menu then try this using Multiple Task Sequences via PXE, PXE boot to a task sequence menu choice is sometimes a good thing or you could consider using a HTA (pretty advanced though...)

it's documented here (the EPP role on CAS etc) http://technet.micro...y/hh508780.aspx you are fine with having it on the standalone primary, but you cannot put it elsewhere (unless of course you are installing a CAS which you are not) as regards storage, you need to think about IOPS,

i'd go with option 1, by the way Endpoint Protection Role must be on the CAS if you are using a heirarchy with CAS installed (and some primaries), but you are not, so you can install it on a standalone Primary instead. you don't really have that busy of a network to manage so the server sounds good enough however you didn't mentioned where/what the 1TB storage is, is it a san or what ?

can you show us the advertisement rerun settings ? (screenshot)

are you sure its the same ts or another ts/advertisement ?

dont try it, only use the recommended supported route. Setup will fail.

in your scanstate.log file, right at the top of the log, it will list the exact scanstate command used, post that here.

welcome ! thank you so much, great to hear it ! as regards your plans on setting up ConfigMgr 2007, why not skip that altogether and go with the brand new product, ConfigMgr 2012, it would make a lot more sense in every way, also are you planning on setting this up using virtual servers or real ? are you setting up a lab first to test things out that you will do in production ?

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