anyweb

Microsoft has been thinking about Windows 8 for a while now even through the production of Windows 7. Some information has been gathered by our friends over at Ars, and all of this said information points to possible 128-bit versions of Windows 8 and definite 128-bit versions of Windows 9. Update: Other technophiles better-versed than I in this whole 64/128-bit business pointed out that it must be for the filesystem (such as ZFS described in this article) rather than the processor and memory scheme. It was obvious that 128-bit operating systems would be rolling out sooner or later, but the only question was who and when. First, of course, we'll need to have 128-bit processors available to the general public, not to mention other compatible hardware and drivers, but there is plenty of time for Intel and AMD (let's not forget ARM who are making strides in their market) to duke that out on the processor field. The information found that suggested 128-bit support by Windows 8 and/or 9 was in a LinkedIn profile of a certain Robert Morgan, who happens to be from Senior Research and Development at Microsoft. The information was afterwards taken down, but luckily it's been preserved on news sites such as OSNews: more > http://www.osnews.com/story/22301/128-Bit_Support_in_Windows_8_9_

what boot image did you use with the task sequence you created, right click on the task sequence and look at its properties

Step 6. Create and Update Distribution Points Select the Package we have just created (Configuration Manager Client Installation) and expand it, Right-Click on Distribution Points and choose new distribution points Select the standard distribution point only and click next when it's done copying, click close Now that you have created the distribution point, right click on Distribution points again, and choose Update Distribution points, answer Yes when prompted Continue to Part 2 >>

check appdeploy.com and see what switches they provide for installing this software, the error code of -1 means it didn't install properly, the error code for a successful install in sccm is usually =0

ok and have you set a boundary for the computers that are in a workgroup ?

mdt 2010 doesn't support that anymore (unknown computer using PXE filter), so use mdt2008 sp1 for that guide or use SCCM 2007 sp2 RC with mdt 2010 and ignore this step. cheers niall

can you raise a separate topic for it and include logs

hi all the site was updated to version 3.04 today by IPB, this should have resolved any issues with editing posts, annoucements and other oddities, if you notice any problems please let us know by posting here cheers niall

the computer most likely has X64 support in it's cpu most do nowadays., the last task sequence advertised to this collection must have had a X64 boot image in it, can you confirm that ?

if you want to deploy vista using PXE boot via SCCM then you'll need WDS installed. do all your configuring in SCCM. cheers niall

this is great please keep them coming

you only have to extend active directory for the domain that both servers are members of.

you dont need to change WDS at all, the suggestions in the guide are for a lab where WDS was the sole method of deployment prior to SCCM, use what works for you, and test everything.

if you have more than one PXE boot server you can use a WDS trick to choose which PXE server to boot from see here

the full edit problem is related to the forum character set, if i set it to iso-8859-1 then we see the problem, if i set it to UTF-8 then it works fine, IPB are working on it right now and are upgrading the forum to a newer version so let's see what happens cheers niall

have you installed the SLP role (server location point) on your SCCM server

how did you configure SCCM to begin with ? did you delete the certificate ? did you leave out any important steps,

how are you running the program from within SCCM ?

indeed, try it ! SELECT * FROM Win32_ComputerSystem WHERE Model Like "%Latitude%"

so that others can learn can you please post the manual changes you made to that file cheers niall

and the account that you installed sccm with and are using is a local administrator of the server ? I had no such problems, have you tried to uninstall the WAIK in programs and features, reboot, reinstall the waik or reinstall the RC sp2 ?

i meant that you would start a new topic (new post) with a description of your problem and any log files associated with it cheers niall

hi there yes it will I run USMT scanstate from Within windows XP, here is an example of a hardlinking task sequence from XP to 7 ts_windows_with_hardlinking.zip (from Jannes) of course you will have to replace the packages mentioned in the TS with your own, and here's some info from Peter's blog about hardlinking cheers niall

when i mentioned Run As I was referring to the MDT integration, ie: can you please install the MDT integration using RUN AS once done, try recreating the boot image

what solution are you using currently ? and why are you looking for a new solution, what features are you missing or looking for