3. party imaging winpe.wim

I am trying to upload winpe.wim to my server but just gets "Unable to mount the selected WIM file. Access is denied"
system is w2k8 R2, 64
waik from : Download details: Windows® AIK for Windows® 7
ZCM 10.3 beta 3
anyone else seen this?

You could try running your browser as administrator - if you GPO's allow it.
Originally Posted by gbarvang
It seems we have a GPO that locks down to much for the domain users, tried it on a single server outside domain and it was no problem.
Maybe docs should be updated with what rights the logged on user/zen service user must have to complete this? I don't know if this is done through the _z* user or as the current logged on domain user.

Similar Messages

64 bit Third party imaging

We are needing to deploy Windows 7 64 bit and to do this we will need to use
a 64 bit WinPE image.
We have setup Third party imaging and uploaded a 64 bit WinPE image and 64
bit imagex.exe. However when zenworktodo.exe is launched it errors because
it is a 32 bit application. (WOW64 does not exist in PE). This seems a
little odd. So my question: Does ZCM have a 64 bit zenworktodo.exe?
We are using ZCM 10.2.2 on OES2.
Bryon
Yesterday it worked.
Today it is not working.
Windows is like that.

Let me know how you get on.
>>> Bryon Nichols<[email protected]> 26 March 2010 23:39 >>>
According to the Microsoft documentation to install a 64 bit os you have to
use a 64 bit WinPE:
http://technet.microsoft.com/en-us/l...93(WS.10).aspx under
Limitations.
I have not tested it was just following what I found. I guess it would be
possible to apply a 64 bit wim from a 32 bit PE. I will be testing that
shortly. As our current thought for a workaround is to create a hard drive
image with ZCM that has Winpe 64 booting. Once WinPE is loaded into memory
it will wipe the disk and install the OS across the network. This however
looks like it loses the ZCM image safe data, though we are still working on
that.
Bryon
Yesterday it worked.
Today it is not working.
Windows is like that.
>>> Heath Upton<[email protected]> 3/25/2010 7:37 PM >>>
Hi Bryon,
We're pushing Novell for both x86/x64 native WinPE support with x64 versions
of ZENworkToDo. This is something they need to do.
In the meantime, provided you're only imaging using imagex to capture/apply
a Windows 7 x64 image, you should be able to do this with WinPE x86 which is
compatible with ZENworkToDo.
Is there a specific reason why you need to boot WinPE x64?
Regards,
Heath.
>>> Bryon Nichols<bryon@gbd‑nospam‑architects.com> 25 March 2010 21:50
>>>
We are needing to deploy Windows 7 64 bit and to do this we will need to
use
a 64 bit WinPE image.
We have setup Third party imaging and uploaded a 64 bit WinPE image and 64
bit imagex.exe. However when zenworktodo.exe is launched it errors because
it is a 32 bit application. (WOW64 does not exist in PE). This seems a
little odd. So my question: Does ZCM have a 64 bit zenworktodo.exe?
We are using ZCM 10.2.2 on OES2.
Bryon
Yesterday it worked.
Today it is not working.
Windows is like that.

Third party imaging question

Is there a way to use the lite touch installations using the deploymentshare? I want to do this so that I can follow the MS deployment docs for adding drivers and using the unattended installs without having to rebuild images. Has anyone thought of or tried this?
I found that I actually could do this by moving <deploymentshare>\ Boot\Lite_TouchPE_x86.wim to c:\program files\windows aik\tools\petools\x86\
Then upload Lite_Touch_x86.wim form that location so that the ZCM winpe.wim uploader can find the other files it wants.
Then rename Lite_Touch_x86.wim to win winpe.wim in %progfiles%\novell\zenworks\share\tftp\boot\
the only problem is that I cant set any zisdata like "justimaged=true"
anyone? I would really like to use the official MS deployment stuff the way it's meant to be used.

Originally Posted by brianrbenson
Is there a way to use the lite touch installations using the deploymentshare? I want to do this so that I can follow the MS deployment docs for adding drivers and using the unattended installs without having to rebuild images. Has anyone thought of or tried this?
anyone? I would really like to use the official MS deployment stuff the way it's meant to be used.
Ok, asked around a little. As my sources tell me Novell is looking at implementing this in the 11 series, but the actual when depends on which other requests are open and how they are prioritised. You can shoot in an enhancement request to add your prio to it. Don't expect to see an option for this before 11.1.
In the meantime there are ways to do this using ZCM with the deployment tools. There are slides that can be found, one source being here : (sorry, many of this is in Dutch - but the screenshots and English bits might give the needed details) : Windows 7 deployment with ZCM
There is also an updated presentation from BrainShare (Amsterdam) that I can send you along with some tools that enable you to deploy Windows 7 with ZCM using the Microsoft WIAK tools. If interested, PM me (it's a newer version than found on internet).
Don't know all the ins and outs of this just jet as I'll be digging into this the next month.. but from what I've seen, only using WIAK and ZCM + the guidelines in the docs how to use the add-on images correctly.. this gives a very solid way to deploy without the need for all kinds of extras or having to touch the base image with every change.

Third Party Imaging and Preseving Partitions

We're currently using WIM / Imagex for our image - is there anyway to restore an image, and preserve a partition that's already on the disk? As far as I can see, diskpart cleans the disk before restoring.
We'd like to partition off a section of the hard drive to let our users use for editing video, but we'd like to preserve it during the imaging process.
Failling that, does anyone know where the diskpart script is stored in the winpe.wim image, so I can have a play with it?
Thanks

You might be better off researching for another list? There is some info here: ImageX and WIM Image Format
--El
Originally Posted by daniel_99_1999
We're currently using WIM / Imagex for our image - is there anyway to restore an image, and preserve a partition that's already on the disk? As far as I can see, diskpart cleans the disk before restoring.
We'd like to partition off a section of the hard drive to let our users use for editing video, but we'd like to preserve it during the imaging process.
Failling that, does anyone know where the diskpart script is stored in the winpe.wim image, so I can have a play with it?
Thanks

Third party image viewer wanted

My company don't want to invest manpower in developing a good and stable image viewer. Can anyone suggest a good third party solution to present pictures (tiff,jpg etc...) and maybe other documents in a viewer component. I couldn't find a good comparsion of the available tools...
Thanks in advance.
TT

An Acrobat specific user forum may not be the optimal place to ask about the why-n-whatfore of a third party software.
Perhaps the application you are using has a vendor support site or user community?
Be well...

Capture image with .wim and unattend.xml?

Hi,
We captured an image with the default wim of windows 7 + an unattend.xml. Now it seems this unattend.xml was not correctly applied (media center was removed but is still there, some components were installed
but are not etc). Question: when capturing an image, you CAN use a default .wim right? Or should you use “apply operating system from original installation source” to have it applied correctly?
Our problem is that our original task sequence had to many Windows updates and crashed. That’s why we are using offline updates which we include in the capture task sequence.
If we would need to use the "apply operating system from original ..." then we'd need to:
1.capture without updates
2.import this wim into sccm
3.offline update this wim
4.use this for capture WITH updates
Please advise. J.
Jan Hoedt

Have you tried making a package of your unattended.xml and pointing to it in your Apply Operating system step?
If I remember correctly SCCM will make it's own unattended.xml even if one exists in the wim file, using the package of the unattended.xml that you have already created will make it use that one. Looks something like this in the task sequence with the highlighted
yellow parts filled out by your package of the unattended.xml:

Open photos in third-party imaging applications

This question was posted in response to the following article: http://help.adobe.com/en_US/lightroom/using/WS614AAD8C-A239-41bc-B8B3-9B2521BFF1A0.html

jnwbr wrote:
I'm using a plugin to do editing outside of LR. Is there a way to add a feature request that the Copy File Options would remember my settings? Every time I choose to edit I have to reset the options.
Save an external editing preset under a name, in the copy file Options dialog. This name appears in the Edit In.. menu and can be accessed directly from e.g. the Filmstrip by right-clicking on an image.
You can have many presets giving variations of bitdepth and colourspace, for different program executables.

Why would a third party image-caching program like Thumbs Plus display thumbnails for only some PDFs

. . . and not for other PDFs, if all of the PDFs have their page thumbnails embedded in them using Acrobat Standard or Professional?

An Acrobat specific user forum may not be the optimal place to ask about the why-n-whatfore of a third party software.
Perhaps the application you are using has a vendor support site or user community?
Be well...

PXE Boot with UEFI. WDS not sending WinPE wim

I am trying to test PXE booting on devices that only have UEFI and no CSM support.
We are running Windows Server 2008 R2 in our environment.
On the DHCP server, we have option 66 and 67 set. If I change option 67 to SMSBoot\x86\wdsnbp.com and boot a traditional BIOS system (non UEFI) the SCCM server responds and gives me the option to hit F12 and PXE boot. This works without issue and can deploy
images.
I then change option 67 to SMSBoot\x64\wdsmgfw.efi and use a machine that is pure UEFI (meaning UEFI without any legacy support / CSM). The system appears to successfully download the wdsmgfw.efi and font file via TFTP as shown in the WDS logs. However, it
then goes to the next sreen where it is trying to contact the WDS server. AFter retrying for a while it will error out with error 0x102 which I believe translates to ERROR_TIMEOUT
The SMSPXE.log repeats the following:
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>8908f9c4-c345-49ba-b137-af7b0b983584</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="GAS20043" OfferIDTime="7/24/2013 3:12:00 PM" PkgID="GAS00037" PackageVersion="" PackagePath="<a href="http:///SMS_DP_SMSPKG$/GAS00038">http://<IVE
REMOVED THIS>/SMS_DP_SMSPKG$/GAS00038" BootImageID="GAS00038" Mandatory="0"/></ClientIDReply>
SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
00:50:56:01:00:82, DF6A0C42-F909-B518-7B44-3150B662200B: found optional advertisement GAS20043 SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
Looking for bootImage GAS00038 SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
Any idea what may be going on?

Hey,
I am having the following situation:
DP1 = Windows Server 2008 R2 SP1 (Standalone Primary Site Server SCCM 2012 SP1 CU2)
DP2 = Windows Server 2012
UEFI Client: Microsoft Surface Pro (with Microsoft Surface Network Adapter)
BIOS Client: HyperV Virtual machine with Legacy network adapert
DP1; DP2 and DHCPServer all in Subnet1.
(IP Helper is set for DHCPServer for DHCP and for DP1 & DP2 for DHCP and BootP - I checked serveral times if everything is right here)
UEFI Client and BIOS Client in Subnet2.
Situation1 -- Using no DHCP Options and both DPs(DP1 and DP2) WDS running:
UEFI Client - Boots perfectly (contacting Server DP2)
BIOS Client - Boots perfectly (contacting Server DP2)
Situaion2 -- Using no DHCP Options and WDS just running on DP1:
UEFI Client - Does not boot (no error information is provided)
BIOS Client - Does not boot (no Bootfilename recieved)
Situation3 -- Using DHCP Options(Option 66="IP of DP1" Option 67="SMSBoot\x86\wdsnbp.com") and WDS just running on DP1:
UEFI Client - Does not boot (no error information is provided)
BIOS Client - Boots perfectly (contacting Server DP1)
Situation4 -- Using DHCP Options(Option 60="PXEClient" Option 66="IP of DP1" Option 67="SMSBoot\x86\wdsnbp.com") and WDS just running on DP1:
UEFI Client - Boots perfectly (contacting Server DP1)
BIOS Client - Does not boot (taking hours to recieve dhcp options..)
My problem is i am having a lot of location with 2008 R2 SP1 server only (this is why situation 1 is not enough for me :-( ).
Based on this article:
http://ccmexec.com/2013/05/configmgr-2012-uefi-and-pxe-boot-support/
x64 UEFI Devices should work with Server 2008 R2 SP1 (not only Server 2012).
Interesting is I am having ALL files on Server 2008 R2 SP1 like they are on Server 2012 (in SMSBoot\x86 folder, too!)??
Some more ideas?
Thank you for help

Customized WinPE with zenworks third party?

I used MDT to create my own deployment share, when you update the share, it creates its own custom windows pe iso/wim files so you can boot with your personalized settings or automate the process. I don't think zenworks lets you import these custom files into the Third Party Imaging Settings, at least I'm having trouble getting them to accept. Seems that it'll only accept the files that come with the MS ADK. This is a bummer, if true. Might have to ditch zen imaging and go with windows deployment server. :\
Not having much luck finding anyone who has experience with MDT/Zen

After Installing the ZCM Agent Initially, If you immediately remote the
"Initial-Web-Service" File, it will not automatically register.
Then after restoring the image, during the Sysprep Deployment phase, you
restore the file and the agent will then try to register next restart or
agent refresh.
On 4/24/2014 2:26 PM, joebrug wrote:
>
> Thats an option I guess.. I'm messing with installing the Novell Client
> and Zenworks agent inside the image, but then have to make sure it
> doesn't register, etc.. cause it goes through a couple of reboots in the
> Windows PE environment to capture an image. I can't find many people
> out there that use Windows MDT + Novell Client + Zenworks agent
>
>
Craig Wilson - MCNE, MCSE, CCNA
Novell Technical Support Engineer
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.

WinPe boot images

I created WinPe boot images from Windows AIK, Windows AIK was installed on a Windows 7 machine. Once Winpe wims were generated I moved them to sccm and imported the images to sccm, images were successfully distributed to DP. The question is when I am adding
drivers and I want to add drivers to my WinPe, they do not show up on the list. where have I gone wrong?

Perhaps Johan's excellent OSD Matrix will help you understand the requirements a bit more:
http://www.deploymentresearch.com/Research/tabid/62/EntryId/127/What-if-I-told-you-The-OSD-Support-Matrix-for-MDT-and-ConfigMgr-is-here.aspx
If you're using ConfigMgr 2012 R2 to deploy Windows 7 SP1, you should be using a WinPE 5.0 (or 5.1 it doesnt matter) image. WinPE 4.0 is not supported in ConfigMgr 2012 R2, nor are WinPE 3.1. You can still import these boot images, but you'll not be able
to amend them like adding drivers etc.
Regards,
Nickolaj Andersen | www.scconfigmgr.com |
@NickolajA

Once an OS image has been distributed to the distribution point, do I keep the source wim as well?

Just curious what do all you SCCM masters do?,
I really don't know if I explain can this right, but here goes.
If I capture a pre-installed/pre-configured imaged to my sccm server to a folder called OSIMAGES, lets call the image myosimage.wim, once I have distributed content of myosimage.wim to the distribution point, do I really need to keep the source copy of myosimage.wim
in the folder OSIMAGES?

Well how does the ConfigMgr know if the content is correct and intact, if it cannot compare it to the one in the source? Do not remove the sources.
http://blogs.technet.com/b/configmgrdogs/archive/2012/04/16/configmgr-2012-content-library-overview.aspx

Error when making an image backup to external harddrive: Files on Z-drive unable to access.

Hello, this is the 3rd time I have this problem. Every time after a major Windows (mine is Vista) update R&R does no longer work.
When I start to create a full image back-up I get some 2 times 5 error messages saying something like: Unable to access or copy to/from
5 times the message z:\tvtos\winpe.wim error 1393 = disk structure problem er something
5 times the message z:\Preload\drivers\E1e5032.SYS Error 5 no access
I may or may not get a message: " Fcopier MFC application is not functioning" (during the copy to/from z: ),
then after 30 minutes the backup gets cancelled automatically.
I assume the Z disk is a virtual memory disk.
I had stopped my virusprotection, firewall software.
I have run this as Administartor
The problem is the same when I run the R&R as Administrator ( I am).
Then after tens of minutes the backup operation gets automatically cancelled.
I have not been able to find a fix for this problem, but before it was fixed by a Lenovo R&R update.
Thanks,

Lenovo Toolbox Warning:
No system backup has been made for the past 212 days.. and counting
I really do not understand this Lenovo support attitude. How can anybody that is customer focused and enjoys his/her job, just fully ignore a customer problems ??
Only one retired employee that is interested (thanks for that) but can not do much.

Image Capture Boot Image Fails with 0xc000000f

I am trying to capture a Windows 8.1 Enterprise (with Update) x64 installation using WDS, but the Capture Image fails to load. I used the boot.wim from the Windows Server 2012 R2 (with Update) ISO to create a boot image in WDS and then a capture image from
it. After I press F12 and the progress bar finishes the following message appears:
This only happens when I boot the capture image - the original boot image that I imported in WDS boots normally. I also tried with the Windows 8.1 (with Update) boot.wim, but the issue reoccurs. This is a Hyper-V VM on Windows Server
2012. Is this a problem with the recent update?

Hi,
We’re currently experiencing exactly the same issue. Also a fully-updated Server 2012R2 (with the recent KB2919355 update) machine.
So far, I found two other posts with exactly the same issue:
1) http://wp.secretnest.info/?p=1474
2)
http://community.spiceworks.com/topic/472581-wds-capture-image-winload-exe-corrupt-or-missing
According to these posts it seems like the issue occurs after the first time a capture image based upon a Windows 8.1 or Server2012R2 boot.wim is created.
What I’ve tried so far is removing the server role, deleting the WDS store, rebooting the server and start over with a Windows 7 boot.wim. The normal boot.wim starts ok, but the created capture image doesn’t.
So the process of creating the capture boot image did ‘something’ in a way the new boot.wim differences from the old boot.wim. To find out what, I first mounted the new .wim file to see if winload.exe is actually there – it is both in
system32 as well as systen32\boot. So my second guess was that the Windows Boot Manager cannot find the windows loader, because of an incorrect declaration of disks in the BCD store.
I used BCDEDIT to show the differences between the working and non-working boot images:
Windows Boot Loader
identifier {1d214c07-6892-401c-a762-04647ad38560}
device ramdisk=[boot]\Boot\x64\Images\boot.wim,{b321afc0-8a23-4
961-85dd-a10f3c46473f}
description Windows 7 Boot Image
osdevice ramdisk=[boot]\Boot\x64\Images\boot.wim,{68d9e51c-a129-4
ee1-9725-2ab00a957daf}
systemroot \WINDOWS
detecthal Yes
winpe Yes
Device options
identifier {b321afc0-8a23-4961-85dd-a10f3c46473f}
inherit {68d9e51c-a129-4ee1-9725-2ab00a957daf}
ramdiskmcenabled No
ramdiskmctftpfallback Yes
-- Second - Non Working disk --
Windows Boot Loader
identifier {872352a0-0ad9-46f6-8612-1aed71ea8534}
device ramdisk=[boot]\Boot\x64\Images\boot-win7-capture.wim,{7a
b86a3a-3651-4f50-a748-34f3e784158c}
description Windows 7 Capture
osdevice ramdisk=[boot]\Boot\x64\Images\boot-win7-capture.wim,{68
d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot \WINDOWS
detecthal Yes
winpe Yes
Device options
identifier {7ab86a3a-3651-4f50-a748-34f3e784158c}
inherit {68d9e51c-a129-4ee1-9725-2ab00a957daf}
ramdiskmcenabled No
ramdiskmctftpfallback Yes
So the ID for the osdevice is the same, and only the device is different, but mentioned correctly under Device options (as far as my knowledge goes in this subject). I hope there will be a solution anytime soon.

MDT Boot Image Creation

I just upgraded my SCCM 2012 RTM to SP1 and then to R2
I uninstalled the WAIK and installed 8.1 ADK
MDT 2012 Update 1
Now I am trying to add new MDT Boot images and I get this error
Started processing.
Creating boot image.
Copying WIM file.
Error while importing Microsoft Deployment Toolkit Task Sequence.
System.Exception: Unhandled exception occurred:
System.IO.FileNotFoundException: Could not find file '\winpe.wim'.
File name: '\winpe.wim'
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileInfo.get_Length()
at Microsoft.BDD.Core.DEInfo..ctor(FileInfo theFile)
at Microsoft.BDD.Core.DirectoryUtility.BeginCopyFile(String theSourceFile, String theDestFile)
at Microsoft.BDD.ElevatedProxy.NewBootImage.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
Jacob

You need to remove the old MDT integration components and then reintegrate MDT with the new R2 installation of Configuration Manager by running the Configure ConfigMgr Integration utility from the start menu (inside the Microsoft Deployment Toolkit folder)
, if your on Server 2012 make sure you run the utility as an administrator (elevated) otherwise it will fail.
If you haven't already done so you will also need to update MDT to 2013 as 2012 Update 1 isn't supported in R2.
Its also a good idea to create new MDT Integrated Task Sequences and copy over any custom actions from your old ones to the new ones.
Cheers
Damon

3. party imaging winpe.wim

Similar Messages

Maybe you are looking for