Video Screencast Help

Comments 82 CommentsJump to latest comment

R Gines's picture

WinPE 3.0 is very high on our roadmap requirements list. Stay tuned, it's coming.

-2
Login to vote
Pascal KOTTE's picture

If you can now think integrating WinPE4.0, should be a best :)

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-3
Login to vote
Nicolas Horchower's picture

Don't be shy, directly schedule winPE5 now ;)

 

More seriously, it would be nice to add an option to ease the merge with DART. Best would be to have easy tools to generate :

-small footprint winPE boot image (for PXE suppport)

-max feature (including ghost and other symantec things like SMP agent, and MS DART for MDOP subscribers) winPE image to create an auto recovery embedded partition.

 

If it is possible to merge agent with recovery partition, we should be able to generate events, when a machine connected to the network boot in recovery mode, and maybe we should be able to automate and log things.

 

Today we manually generate partly this (MDOP requires the same winPE level version) and we also create USB stick for machines without recovery partition (or not mountable HD).

--
NH

-3
Login to vote
willson's picture

hi rick

my problem is...

Currently some desktop computers on the lan are having gigabyte 945 intel chipset motherboard with C2D 2.93 GHZ processor and 4 gb ddr2 RAM ; Windows XP is installed along with other softwares from the network from altiris server .
According to Company's  New IT policy all systems with windows xp have to  be shifted to Windows 7 64 Bit.
We have sucsessfully installed windows 7 professional 64 bit on standalone desktop for testing purpose(via DVD  rom) but when we try installation through lan from altiris server we are unable to install windows 7 professional 64 bit , according to our customer end IT administrator  the system is throwing  "windows PE" error; we also tried latest G41 motherboard but we are getting the same error whereas  Dell and HP desktop computers are being installed successfully with windows 7 64 bit from the same altiris server through the same local area network.
 

please give me a solution for same

Thanks

Willson

-1
Login to vote
willson's picture

Depyoment of windows7 through altiris server

hi rick

my problem is...

Currently some desktop computers on the lan are having gigabyte 945 intel chipset motherboard with C2D 2.93 GHZ processor and 4 gb ddr2 RAM ; Windows XP is installed along with other softwares from the network from altiris server .
According to Company's  New IT policy all systems with windows xp have to  be shifted to Windows 7 64 Bit.
We have sucsessfully installed windows 7 professional 64 bit on standalone desktop for testing purpose(via DVD  rom) but when we try installation through lan from altiris server we are unable to install windows 7 professional 64 bit , according to our customer end IT administrator  the system is throwing  "windows PE" error; we also tried latest G41 motherboard but we are getting the same error whereas  Dell and HP desktop computers are being installed successfully with windows 7 64 bit from the same altiris server through the same local area network.
 

please give me a solution for same

Thanks

Willson

-3
Login to vote
willson's picture

Depyoment of windows7 through altiris server

hi rick

my problem is...

Currently some desktop computers on the lan are having gigabyte 945 intel chipset motherboard with C2D 2.93 GHZ processor and 4 gb ddr2 RAM ; Windows XP is installed along with other softwares from the network from altiris server .
According to Company's  New IT policy all systems with windows xp have to  be shifted to Windows 7 64 Bit.
We have sucsessfully installed windows 7 professional 64 bit on standalone desktop for testing purpose(via DVD  rom) but when we try installation through lan from altiris server we are unable to install windows 7 professional 64 bit , according to our customer end IT administrator  the system is throwing  "windows PE" error; we also tried latest G41 motherboard but we are getting the same error whereas  Dell and HP desktop computers are being installed successfully with windows 7 64 bit from the same altiris server through the same local area network.
 

please give me a solution for same

Thanks

Willson

-3
Login to vote
SK's picture

Hello Wilson,

Without the actual error, we cannot determine what the true problem is here; however, I suspect that it is most likely due to WinPE 2.1 not having the relevant drivers for those new models.

You can check this out via the Boot Disk Creator, and if the are missing, you ca download them from the vendor and then add them to WinPE.

PS: There is no need for multiple posts.  One submission is adequate.  ;-)

SK

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

-3
Login to vote
arjain's picture

It seem that you are using SOI Windows feature to install Windows x64bit, pl make sure taht you have booted your machine in Win PE mode either through Automation folder or through PXE should be in 64 bit.

This can be checked from the title bar of command prompt.

~ SQA Manual - Crafting tomorrow

If a forum post solves your problem, please flag it as a solution. If you like an article or blog post vote for it.

-3
Login to vote
Pascal KOTTE's picture

SOI ?? oh my god, another abreviation ! Is it in Wikipedia... not yet!

Be Careful all that for SOI, alias "Scripted OS Installation", you need to use a preboot x64 for Win7 64bits, and x86 for Win7 32bit.

Notice: the "default configuration file" is not working. ("no found image" error): Must use a custom one. If you create a preboot with both x64+x86: possible not be able to "select" if your preboot will be x86, or x64: automatic detected from preboot. So if you miss some drivers and want to "force" a preboot x86 for x64 machines: need to create 2 preboot: 1 is only x86, another is only x64. But loose the single "SOI" task. must build 2 and having a good filter to separate "machines to use preboot x86", "machines to use preboot x64".

Also be carefull: If you create 2 preboots; and you are a litlle bit surprise only 1 showed in the menu when modify an existing job/policy:

  • delete the existing "name" to empty the field, before selecting the combobox menu,
  • you will avoid the "default name filter" bug :)

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-3
Login to vote
Pascal KOTTE's picture

SOI default config file was not working, using VMplayer AMD64 machine, 7.1 MR1 (March 2011, before SP1 June)...

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-3
Login to vote
Pascal KOTTE's picture

Be aware that for WinPE 2.1, for making it works correctly for seeing the Disk & network card, you must upload the Vista Driver:

  • If not the net driver: DHCP reply repeat message on preboot !!
  • If not the disk driver: ghost error

You can cumul the 2 problem :)

Also, if installing both winPE 2.1 x86 & x64, installing the x86 drivers only, does not update the x64 preboot. Be sure not switch the 2 winPE.

Best practices, choose x86 and never install x64 for winPE2.1, because more easy to find x86 vista drivers than x64, and avoid double updating need. But can switch according your own environment.

Another alternative for nice preboot, use Linux, but of course also need good drivers... But from time to time, some drivers are in linux, not the winpe 2.1 :)

Enjoy PXE preboot, hope some improvement into next altiris, to automate those ...#@^X!... drivers updates.

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-3
Login to vote
Pascal KOTTE's picture

I said x86 for WinPE 2.1, when 3.0 there, use only x64 preboot wink

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
WHITE EAGLE's picture

I  suggest;

Submit update and review all your support cases online.

And you need to know if symantec traffic shapper support SESA integration.

-1
Login to vote
qman_au's picture

I have successfully managed to integrate WinPE3.0 and create PXE boot images using PXE Config Manager. Having Issues trying to get WinPE3.1 to work though. Mainly want WinPE 3.1 so i can get the support for Advanced Format HDDs using 4k sectors. Might have to just patch the WinPE3.0 with the hotfixes to make it work with 4k sector drives. Would be nice to have a proper Symantec WinPE3.0/3.1 solution though instead of hacking it myself....

-3
Login to vote
qman_au's picture

Yay! Managed to implement WinPE3.1 into Altiris DS 6.9 SP5.

IMG_0270[1].jpg
-3
Login to vote
powellbc's picture

Care to share how you did this? :)

-3
Login to vote
qman_au's picture

Here is an example, your folder structure may be different to mine.

Install WAIK 3.0 and update with WAIKS 3.1.

copy C:\Program Files\Windows AIK\Tools\PETools\x86\winpe.wim -> D:\Program Files\Altiris\express\Deployment Server\WAIK\Tool\PETools\winpe.wim

copy the following cab files (winpe-wmi.cab, winpe-scripting.cab, winpe-hta.cab) from C:\Program Files\Windows AIK\Tools\PETools\x86\winpe_fps -> D:\package

copy any win7 drivers you will need in the winpe boot file to d:\driver

DSIM /mount-wim /wimfile:D:\Program Files\Altiris\express\Deployment Server\WAIK\Tool\PETools\winpe.wim /index:1 /mountdir:d:\mount

DISM /image:d:\mount /add-package /packagepath:d:\package

DISM /image:d:\mount /add-driver /driver:d:\driver /recurse

DISM /unmount-wim /mountdir:d:\mount /commit

Now use PXE config manager to create a new winpe boot image. It will utilise the new winpe3.1 winpe.wim file and create the "winpe2.1" image from that. Once all is finshed, as long as pxe config manager shows that the boot file is winpe2.1 then all should be good. If pxe config manager only shows the boot file as "winpe", then it wont show up as a valid selectable winpe boot image. The only way around it I have found is to reinstall DS. This has been tested on DS 6.9 SP4 & SP5.

Hope that helps.

+6
Login to vote
donparfet's picture

I am testing installing DS6.9Sp5 on Windows Server 2008 R2 Standard (64bit) and I have followed your instructions here and have successfully created a WinPE 3.1 boot image, but the Altiris Agent fails to communicate with the server successfully. I wonder if I might bend your ear to understand better what you have done to gain success. The main reason we wish to image with WinPE 3.1 is this seems to be required in order to configure the Win7 partitions to support built-in Win7 file encryption

0
Login to vote
valentino3m's picture

Symantec Dev, you need to get off your lazy behinds and update your WinPE pre boot OS to 3.1.

WinPE 3.0 has been out since 2009 for goodness sakes, and since the release of Win 7 SP1 its now 3.1. Get with the times Symantec.

Thanks to qman_au it now only takes only 5 minutes to upgrade Symantec's very old WinPE 2.1 boot OS to 3.1, and it works a treat!

Keep up the good work qman_au!

PS. to other users, if you have an option to use DS 6.9 over DS 7.1, stick with 6.9.
 

-3
Login to vote
Pascal KOTTE's picture

Can it be possible doing similar job, for DS 7.1?

Is is a shame users must do this job themself instead of getting that from Symantec. I am ok need in depth testing, and so on. But Symantec can also publish "in there" as beta code: and receive feedback from Connect. Keep it simple & quick Symantec. World will not wait after you are ready, and some my customers already use WAIK & Microsoft MDT instead of Altiris any more.

For users, please join your nearest "Altiris user group", and publish your top priority requests to Symantec.

For "user group Management board members": Please, contact me, to share your top priority requests.

For "partners": Perhaps we should think a "partner group"...

We really need to explain all together to Symantec our "Top" priority expectations. Too much energy at Symantec for lot of "presales tools & data", and not enough for quick & quality code production. Thanks again your post.

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
qman_au's picture

No idea on DS 7.1. Dont use it and I doubt we will move to it.

I have already posted a topic on altirigos.com linking to this post.... I have been using the Winpe3.0 hack for over 18months now...surprised that I have not seen anyone else mention this workaround.

-3
Login to vote
Pascal KOTTE's picture

Seems documentation & support told about max 20 PXE,

We have in production a couple customers with 60 PXE slaves the same DS6: For sure, must trigger PXE config helper stop & restart from NS task :)

But it is working !

What about 200 ? Possible, or not ?

I figure out DS 7.1 was able to manage more 200 sites (about 2'000 machines), better than DS 6.9, but seems I am wrong ?

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-3
Login to vote
LShackleton's picture

But I'm curious what reasons I'm obviously unaware of that makes people so desperate to use 3.x and run unsupported, can anyone enlighten me?

I've been imaging with Win7 since DS 6.9 SP3 release month and I've not encountered any problems so I'm just curious what I can expect from WinPE 3.x since I'm not familiar, at least in terms of functionality related to performing DS automation tasks.

Cheers for any responses!

-3
Login to vote
ACassar's picture

Not sure about the others posting here,  but in our case, we are using the Automation environment to perform alot of offline servicing of our Windows 7 image at imaging time.  Specifically, Offline patching, Installation of Drivers and Installation of Language packs.

This worked fine using PE2 and Win7 RTM,  however with the release of Win7 SP1 and the SP1 language packs our ability to offline install language packs (Specicially Japanese) stopped working.

After a ticket to Microsoft we were advised that in order for any form of Win7 offline servicing to be supported by MS,  that PE3 at a minimum was required and 3.1 recommended for SP1 servicing.  Then surprisingly as soon as we went to PE3.1, our offline servicing problems were solved and we could install the Language packs again.

 

 

On another note,  we have found that when using PE3 our dagent keeps connecting use Multicast (a Multicast address is displayed on the dagent UI instaled of (Connected via TCP)). Because we dont use Multicast in our environment,  this causes Rdeploy (which we use for our old XP build) to fail when deploying more than one machine simulatniously.  Ive gone through every single script in the PE image to try to find how this is being set to multicast,  but cant for the life of me find it (the aclient.inp and everything seems to be set to TCP)..  has anyone else come accross this?  If i use the default PE2.1 image from boot disk creator it connects via direct TCP.

+1
Login to vote
qman_au's picture

Adam,

we have a build room which has a DS 6.9 SP4 in it. It is running WinPE3.1 and has no issues with multiple builds at the one time. I have not checked to see if it is connecting via MultiCast or direct connect TCP/IP.

-3
Login to vote
gamgee's picture

@Adam

We were experiencing the same issue with Rdeploy failing if you tried to image more than one client simultaneously, after incorporating PE 3.1 into our PXE images (DS 6.9 SP5).

 

In the end we found that in our case it wasn't anything to do with the agent connection, but rather, because the account used to map the express share within PXE had modify rights (on the share), the first client to load the actual RDeploy.exe executable file was locking the file for write access and preventing any other clients from accessing the file. Once we modified the NTFS permissions on the RDeploy.exe file to allow read access only, the problem disappeared. It took me while to figure this one out because we didn't observe this behaviour with our old PE 2.1 boot images, it only surfaced after we made the switch to PE 3.1.

 

Not sure if this is the same problem you're having but hopefully it will help someone else out, as I was pulling my hair out over this one :)

+3
Login to vote
ACassar's picture

Gamgee,

You are my hero.. This was the exact cause of our problem.  We had been pulling our hair out for weeks.  I got as far as checking locks on the actual image, but didnt think to check the locks on the rdeploy executables.  I guess the multicast address that was showing up in the dagent config screen was just a red herring. 

Thanks so much for taking the time to reply.  It certainly is appreciated.

Adam

-3
Login to vote
qman_au's picture

WinPE3.1 will provide native support for Advanced Format HDDs which are 4k sector based and not 512byte. I had issues with DiskPart under WinPE 2.1, as we use scripts to deploy our Wim images as DS6.9 has fixed switches for deploying Wim images.

+1
Login to vote
Pascal KOTTE's picture

Better support for not integrated drivers. When need to integrate new hardware, it is not fun to duplicate the job load for integrating those for vista, and others for Win7: better to use a single driver for both, preboot and OSD.

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+2
Login to vote
JoeZeppy412's picture

For one thing, we have no Vista machines, no Vista drivers, so why would I support vista PE?

WinPE 3.0 can include remote access via components copied from MSDaRT 7.0. Very helpful when a deployment is failing or stopped on another site. We have PE set up to create a shortcut on a server so we can click on it and instantly remote to a deployment in process.

http://www.deploymentresearch.com/Blog/tabid/62/En...

We also PXE boot to WinPE to run our standalone legacy XP ghost process via an HTA menu, and any offline PC management. My WinPE is pretty customized as a utility boot image, for BartPE type use.

Now that we're switching from MDT 2010 to DS 7.1, it feels like I'm taking a major step backwards. (Maybe switching, our Bay Dynamics consultant is pretty clueless, doesnt seem to know much about Win 7 and cant answer basic questions about how DS works in comparison to MDT).

DeployAnywhere driver database in particular seems stone-age. No folders or any way to organize drivers per model. Doesn't look like theres any way to limit driver install so for example we don't get Dell drivers loading on HP machines, etcetera.

We have about 6 - 7 gb of drivers in our MDT driver store. How do I manage that effectively in a flat file list like DeployAnywhere? Plus, takes forever to load. Color me unimpressed.

WinPE 4 will support PowerShell. Any chance we'll see that from Symantec within 5 years or so?

+1
Login to vote
ravenzod's picture

One more reason to go for WinPE 3.x is when we receive new PCs with hardware that isn't supported by WinPE 2.1 (e.g. the Intel NICs in Dell Optiplex 990s or Latitude 6520s) we prefer to only download the Win7 drivers. Soon we will completely migrate to Win7 and although Vista drivers are available for WinPE 2.1 its still more overhead and an easy thing to miss that WinPE 2.1 sometimes specifically require the Vista driver.

I read in Adam Cassars' post he was advised by Microsoft to upgrade to WinPE 3.1 by Microsoft. Although this is the obvious easy answer, it seems required for support..and since out since 2009 (WinPE 3.0 that is, it does seem time for Symantec to make the switch).

Thanksfully DS 6.9 is still supported by Symantec. We're upgrading our NS to 7.1 but are staying on DS 6.9 for now (different server) until everything is stabilises and our migration of 1600 nodes to Win7 x64 has been completed.

+2
Login to vote
james_g's picture

WinPE 3.0 has been in place for awhile, WinPE 3.1 is already reved = no one in their right mind in an enterprise would not be using this version for its flixibility, maturity and configurability !

it's coming = when ?

+1
Login to vote
Geek786's picture

Still on its way or lost its path :))

-1
Login to vote
Sweeten's picture

bump? is this still happening? seems like this should have taken about an hour of dev time including basic testing/bug squashing

-1
Login to vote
Geek786's picture

DS 7.5 is coming in fall with WinPE3.0 or 3.1

-3
Login to vote
Sweeten's picture

We have no plans, nor desire, to move to 7.x unless it starts behaving more like 6.9. Thanks for the response, though.

+3
Login to vote
LShackleton's picture

I wonder how many customers are in the same boat. We also have no plans to move to 7.x (for DS - we moved our NS to 7.1 long ago) for what we see as an inferior deployment solution for our needs. For all the core products we use we feel totally abandoned by Symantec and DS 6.9 is at this point the only reason we still pay our renewals.

+2
Login to vote
drheim's picture

So I created a winpe3.0 following qman_au instructions, but where do I put that file on altiris 7.1 servers? Do I rename \\notificationserver\Deployment\Task Handler\WAIK\Tools\PETools\x86\winpe.wim file and then throw it in there?  Then tell it to create a new Preboot configuration?  When it creates it, will it add the Altiris agent in so it will process commands?

 

Also,

FYI - I went through qman_au instructions for everything exactly for 3.1 and could never get it to work.  I was really careful with my file handling and tried on (2)different computers, but could never get it to add the scripting packages in using the dism commands.  The error coming back was always "The specified package is not applicable to this image" and I triple checked the x86 and made sure I grabbed the packages under the en-us folder, but never could get it to work for x86 or x64.  I googled the error in the dism log file and there is a bug and I tried to go through the suggestions there as well, but nothing ever worked on either computer.

-3
Login to vote
XB's picture

LinuxPE too.

I want to tag to this idea.

Next versions of DS should not only support newer versions of WinPE but also newer versions of LinuxPE.

As an example, the newest HP thinclient T610 will not start the standard LinuxPE provided in DS 6.9 SP5. Testing showed that it will not start from OpenSuse 11.1 either, but OpenSuse 11.4 works fine.

If a Connect post helped you out, be sure to click "Mark As Solution" or the "Thumbs Up" button to let other users know about it.

-3
Login to vote
dcuoq's picture

Thanks for the share. My WinPE 3.1 works fine for me on my DS 6.9 SP5.

Somebody have tested WinPE 4 ? is there something change for exemple capture or deploy wim image (size of the wim is the same with WinPE 3.1 and 4.0 ?).
I know that 3 bests parts for this new release WinPE 4 :
- WinePE 4 boot faster than 3.1
- .Net Framework
- PowerShell 3 ^^

Enjoy Altiris Guru

Cordialement | Best Regards
DAVID CUOQ
Coordinateur Technique Micro-Informatique
a-SIS

-3
Login to vote
Maymne's picture

Tried WinPE4 today following the same directions as WinPE3.1 above. Gets partially through the compression and then says Access denied, folder is not empty. Would love it to work, but... seems more complicated. Restored the winpe.wim files from WinPE2 that I'd made as backups and it rebuilt another copy of the boot files just fine, so the error appears specific to the WinPE4 files.

-1
Login to vote
donparfet's picture

We have addressed using DS 6.9 and Advanced Format Drives via the following method:

1. Build a WinPE 3.1 disk, use diskpart to format and prepare the AFD correctly

2. Load the win7 wim and update it accorgingly

3. Once updated, copy the wim up to our DS server

prepare a new machine

1. Prepare the disk using the WinPE 3.1 disk and diskpart

2. boot to DS (using the built-in WinPE2.x distro) and copy the wim to the new machine pre-prepared hard drive

3. via script, call the winpe 3.1 version of imagex to apply the wim to the drive

once the OS is applied to the drive then the remaining DS functions continue without problem (naming the machine, adding to the domain, scripted installs, etc.)

-3
Login to vote
gerardsweeney's picture

Possibly stupid question for those running with PE 3.1 here..

 

I take it RDeploy remains "broken" so far as AFD drives are concerned? By that I mean that restoring an RDeploy image onto an AFD will result in a partition that is not aligned, and consequently moves like a sloth?

We just purchased a fairly large collection of laptops which we're hoping to put Win7 images onto so I'm not liking the sounds of this.

 

-3
Login to vote
dlee2654's picture

Symantec, ever since the release of the new Dell PowerEdge 12G servers our DS 6.9 no longer works.  We believe this is due to the outdated version of WinPE provided with the product.  Please update your product it is now November of 2012.  If you cant bring yourselves to do this, we will be forced to abandon the Symantec product.  We now must hand load our new 12G servers until this is fixed.

-1
Login to vote
OrArnon's picture

Hi guys,

is there any step that needs to be taken before the following procedure:

Install WAIK 3.0 and update with WAIKS 3.1.

copy C:\Program Files\Windows AIK\Tools\PETools\x86\winpe.wim -> D:\Program Files\Altiris\express\Deployment Server\WAIK\Tool\PETools\winpe.wim

copy the following cab files (winpe-wmi.cab, winpe-scripting.cab, winpe-hta.cab) from C:\Program Files\Windows AIK\Tools\PETools\x86\winpe_fps -> D:\package

copy any win7 drivers you will need in the winpe boot file to d:\driver

DSIM /mount-wim /wimfile:D:\Program Files\Altiris\express\Deployment Server\WAIK\Tool\PETools\winpe.wim /index:1 /mountdir:d:\mount

DISM /image:d:\mount /add-package /packagepath:d:\package

DISM /image:d:\mount /add-driver /driver:d:\driver /recurse

DISM /unmount-wim /mountdir:d:\mount /commit

Now use PXE config manager to create a new winpe boot image. It will utilise the new winpe3.1 winpe.wim file and create the "winpe2.1" image from that. Once all is finshed, as long as pxe config manager shows that the boot file is winpe2.1 then all should be good. If pxe config manager only shows the boot file as "winpe", then it wont show up as a valid selectable winpe boot image. The only way around it I have found is to reinstall DS. This has been tested on DS 6.9 SP4 & SP5.

 

1. Do I need to re-create the preboot environment?
2. What of the Altiris agent - it is not compatible with the WinPE 3.1
3. Do I need to create the WinPE with x64 compatibilty only?

-3
Login to vote
qman_au's picture

1. As long as you have already instaled winpe2.1 x86 preboot, you do not need to do anything else.

2. Altiris Agent works independantly of winpe

3. WinPE3.1 x86 is compatible with both x86 & x64 builds of Operating systems. http://technet.microsoft.com/en-us/library/hh824964.aspx

-1
Login to vote
OrArnon's picture

Hi,

can you elaborate on the WinPE 3.1 x86 section?
My logic tells me that since it is Win7 kernel based, it should be x64 alone, so I wasn't sure what checkboxes should be checked.

-1
Login to vote
Ludovic Ferre's picture

What gives you the impression thart Windows 7 is a 64-bit only Kernel?

Windows Server 2008 was the last 32-bit Windows (ever - dixit Jeffrey Richter).

I am currently off-net, on a retreat of some kind. I'll be back real soon, and you sure will hear from me then ;-).

Ludovic FERRÉ
Principal Remote Product Specialist
Symantec

-3
Login to vote
qman_au's picture

Hi,

Any chance we are going to see official WinPE3.1 support for DS6.9 from Symantec?

+1
Login to vote
OrArnon's picture

That's what I meant... so bottom line: What check boxes should be checked when creating the boot image?

-1
Login to vote