ACR not applying linear segment w/ProPhoto

I was using Imatest to check the DR of my Nikon D800e with the Stouffer stepwedge. I was using ACR 7.2 with the Adobe standard profile and PV 2010 with a linear tone curve (sliders set to zero, point curve = linear). When rendering into ProPhotoRGB, I noticed that there was no linear segment at low luminances and the expected linear segment was present with sRGB.
The Imatest plot is shown along with the calculated response using the densities of the step wedge and the ProPhoto equations. The linear segment starts at target densities of -2.5. This causes ProPhoto to have a slightly greater total dynamic range than sRGB. This is no big deal, but my investigation was to investigate an assertion that ProPhotoRGB has a greater dynamic range than sRGB. It is true that saturation clipping occurs earlier with the narrower space, but luminance clipping should and DR should be about the same.

deejjjaaaa wrote:
well, the data that those sensor manufacturers provide for their sensors do not actually exactly reflect the data in the raw files written by firwmare of 3rd party camera manufactureres that are using those sensors, more so that those sensors are probably CCDs with much more circuitry added by actual camera manufacturer like ADC off sensor... and DxO is testing the data in raw files (another story that they are shooting targets that you never encounter in a real life and they use "engineering" definitions of DR)... so what is the beef if a modern small sensor has low readout noise and some big sensor does not ? move towards midtones and picture will better for a big guy... there is no replacement for displacement in the end (unless you use totally obsolete technology).
The engineering definition of DR is an industry standard and is reported on by Kodak and Dalsa (and their successors) in their data sheets. Photographic DR varies according to how much noise one can accept in the shadows, and each observer may have their own opinions. DXO does provide a full SNR plot from which one can calculate the DRs for any given noise floor. Shown are examples for the Nikon D4 and D800e.
The larger CCDs in MFDBs do collect more light and have better SNR in the midtones where their high read noise is relatively low in proportion to shot noise. The question is how much SNR is enough? If you can not see the noise at a given image size, does it matter?

Similar Messages

Exposure slider not entirely linear ?

Ive recently captured an image with a bright, red to orange sky in the background due to sunset conditions. With a linear preset in ACR (all tonal controls zero, parametric and point curve linear) theres no clipping indicated.
Actually the Exposure slider has to be raised to +0.70 in order to drive relevant parts of the sky into clipping. But, the Exposure slider has to be set down to -0.70 in order to detach the histogram from the right end of scale.
In between, its obvious that the histogram does not react linearly to the Exposure slider. Increasing it from 0.70 to +0.70 accumulates and compresses more and more data in the right corner of the histogram (up to RGB 254) without making the final step to clipping.
Output space is set to ProPhoto RGB, Noise reduction and Sharpening are off, the Recovery slider for sure is at zero. Its CS4 + ACR 5.2.
Any thoughts or explanations?
Thanks!
Peter

> You can effectively get linear output from Camera Raw (with the exception of gamma encoding) by creating a custom color profile with the DNG Profile Editor with its Base Tone Curve set to Linear, then use the Camera Raw Defaults when processing your image and select that custom color profile.
Eric, - Many thanks for joining discussion. So what would be the difference between a.) using such linearized custom profile created the way you describe with the DNG profile editor, and b.) employing a linear preset in ACR, means to set all tonal controls to zero, parametric/point curve linear while using the baseline matrix profile ?
Or, let me ask straightforward: could there possibly be something behind my question, or am I barking up the wrong tree ?
> The conversion of the demosaiced raw data from the camera's color space in sRGB, aRGB or ProPhoto RGB includes the non-linear transformation as well. This can not be avoided in ACR to my knowledge
Again my understanding was that matrix-to-matrix conversion is essentially a linear transform (if this is the right term). Means that linear scaling and matrix-to-matrix conversion are essentially commutative, the sequence can be exchanged and the results will be the same (provided that the absolute value of the scaling factor is adjusted) and despite different matrix primaries and different gamma. However, I agree that there are a couple of constraints such as:
/> out of gamut colors
/> fancy 'gamma' e.g. with the sRGB TRC
/> AbsCol conversion between different white points which can introduce additional clipping
/> RelCol conversion between different white points (not sure about this one)
So in order to check my approach of testing, I did some ColorChecker exercises. Processed it through ACR (linear preset) with different Exposure settings. Converted to 'linear gamma' ProPhoto RGB in Photoshop. Finally, all derived ratios R2:R1, G2:G1 and B2:B1 were approx the same, whether this is a color or gray patch which I think confirms linearity.
Seems I still have to find out whats so special with my sunset sky. Or, the hue preserving feature comes in mind which was reported to cover ACRs tone curve(s). Could it be that it acts 'on' the Exposure slider as well, once a single channel is driven into clipping, thus, preventing this. Just a thought.
Many thanks for your comments.
Peter

ACR not using .xmp files after 03/09/2011

I'm using ACR 6.4.1.145 and Bridge CS5 on a Windows 7 x64 Pro machine. Canon S95 and G12 CR2 files created before 04/09/2011 behave exactly as they should: changes aved in .xmp files are recognized and applied in Bridge thumbnails and when the image is re-opened in ACR.
Images created on 04/09/2011 and any later date (tested by altering the file dates) have their changes saved in an .xmp file, but this file is not applied to the thumbnail in Bridge, the Bridge thumbnail does not indicate the .xmp file exists, and the .xmp changes are not applied when the image is reopened unless the .xmp file is loaded manually.
I have purged the cache, restarted Bridge, and restarted Windows. I've moved the images to a different directory, then a different drive. I've loaded the images from the SD card several times now. The problem persists.
All assistance appreciated.

Thanks Thomas.
I am pretty sure the CR2 files don't contain any .xmp data. For one thing, the problem only occurs on my installation. If I use another computer, everything works as it should.
The problem has returned, however. I just tried to make changes in ACR to images created today, and although ACR saves the .xmp, it does not recognize it when I open the image again. I have to load the .xmp manually.
I will bet that tomorrow, the problem has gone away. That would make it somehow time/date dependent. More important to you and anyone else trying to help, it seems to happen only on my installation of CS5. Something has gotten corrupted, I think. If the problem persists, I will probably try a re-install, but I hate the patching proces that follows.

Custom settings of Edit-in Preset not applied to image in PS

I am having a problem with my custom made EDIT-IN Preset. While clicking on it launches the image (dng, psd or tiff) in PS, the custom settings of the preset (in my case: 8bit, sRGB) are not applied to the image. Instead the image is opened in PS with the default settings as specified in the Preference menu (in my case: 16bit, ProPhoto RGB).
I am running LR2.2 & PS CS3 (10.0.1) on a 64bit Windows Vista Business machine.
The settings of the preset are:
Application: Photoshop.exe
File Format: TIFF
Color Space: sRGB
Bit Depth: 8 Bits
Resolution: 240
Compression: None
By the way, this problem occurs also on my 32bit XP-Pro Computer.
Any helpful suggestions?
Mike

Hi,
I think you are running same problem as described in the following article:
http://support2.microsoft.com/kb/2894518
Updates trigger multiple boot is caused TS failing.

ACR not keeping same edit as in Bridge?

In Bridge, my photos are auto toned, and I happen to like the effect most of the time. But when I go to open it in ACR, it does not keep the effect.
I have tried to change the settings and have looked for a way to fix this, but to avail. I want the same edit I see on my photos in Bridge to transfer over to ACR. Because now I have to manually adjust my picture to look like it did in Bridge. Is there an option to keep the same settings?
I use:
ACR 5.7
Bridge CS4
shoot RAW of course.
(by the way, if they say the Bridge can only preview jpegs with the auto tone corrections and must covert to RAW, etc, then why do I see my RAW photos having it? It doesn't make sense.)
Help would be greatly appreciated.
Thank you.

If I set automatic autotoning in Bridge the slider values are the same in ACR as if I clicked Auto inside ACR w/o automatic autotoning enabled. So the autotoning is not different.
And I am not seeing any differences if I make a screen-capture of Bridge's Preview and ACR Preview and quickly alternate back and forth between the two with Windows Photo Viewer or similar. There are no differences with or without autotoning applied.
However, what seems to be true is if you have touched an image with ACR and clicked Done or Open Image rather than Cancel to exit ACR, then Bridge automatic autotoning is NOT applied afterwards in either Bridge or ACR. In other words the automatic autotoning in Bridge is only applied to "virgin" images, not already-adjusted images.
Does this explain what you're seeing?

Do not apply the latest upgrade to LR 4.2 if you are using PS5

Do not apply the latest upgrade to LR 4.2 if you are using PS5. The latest LR update used Raw 7.2 which is not available in CS5.
Wish I had a was to go backward. LR 4.2 was working fine until the latest upgrade.
Wish I had not done it. NOW I am back to all the problems I had when I first installed LR4.0.
Plus I am swamped with work through the Dec. So no time to spend days on the phone with support.
Afraid to upgrade to PS6 as I cannot aford any additional issues. Have lost my faith in adobe.

There is nothing wrong with LR, it always works one way with whatever is the contemporary Photoshop version., and another way with all other software. CS5 is not the contemporary version with these newer Lightroom versions, CS6 is.
If you have the latest PS as well as the latest LR, then the "Edit in Photoshop" command gets ACR to process the file, using LR settings.
If you have different software or older software, either that cannot happen, or else is not certain to happen 100% compatibly. So a different method is used, as JimHess says: getting LR to render the file properly, instead of getting ACR to have a go (and perhaps get some things wrong).
If you get a dialog box warning about ACR compatibility, you need to select "Render using Lightroom" rather than "Open anyway".
If you no longer get this dialog (you have checked "don't show again") you can make it show again using the LR PReferences / general tab / "Reset all warning dialogs" button. That lets you select the proper option.
The only caveat here, is that with this "render using LR" method, the converted file has already been named and saved to disk before you see it in PS. This means that when you finish your edit, you must Save the results to the filename already assigned, not to another name. Then LR will be looking in the right place, to see your PS edits. This also means that even if you don't save changes at all from PS, LR will still show a new image version anyway (unlike with the other method via ACR).

Remote system CCMS segment not in local segments

Hi,
I have configured CCMS agents before but this one is puzzling.
- downloaded latest CCMS agents sar file for PI systems
- I have created the csmconf file and placed in the right locations.
- i started the CCMS agent for PI systems from Visual Admin and it found the csmconf file, i provided the passwords and it started but the segment name is not in "local segments" in RZ21 in SOlMan (Monitoring: Display technical topology) and therefore i am limited to what i can see in RZ20.
- i unregistered the agent and started it at OS level with the -j2ee option and gave the passwords and it still did not come under "local segments".
- the PI systems have remote Databases from which i started the CCMS agents and they do appear under "local segments" and can see them in RZ20.
- their respective CCMS agent are visible under the PI system's RZ21 "local segments" but as far as i remember from the OS level i did not configure it to register itself with PI itself but only with the CEN which is SolMan.
in my other solman systems the remote PI CCMS agents and amongst others are all under "local segments" and they all visible in RZ20.
I want to register the agents for the PI systems so that they appear under the "local segments" tab in solman and i can carry out my monitoring but they do not.
has anyone else had this problem?
Thanks,
Mani

Hi,
Please see if these threads help.
API to load images for
API to load images for
Employee Photo Upload in HRMS
Employee Photo Upload in HRMS
Dispay employee pictures in Employee Self Service screen
Dispay employee pictures in Employee Self Service screen
Regards,
Hussein

Text not printing or PDFing. Non-printing is not applied. Help?

I have a logo. The top is on a path applied to an oval. Same with the bottom. In the middle is an ampersand (&). When I try to print, only the ampersand prints. I've tried printing to 2 different machines. I also tried saving it as a PDF but I lose everything except the ampersand in the middle. Everything is colored black, so there are no weird colors going on. Non-printing is not applied to anything. Any thoughts? I can send the file to somebody if they want to check it out.
ID CS 3
Thanks,
Chris

Sorry for the delay. Spent some time looking for the font becasue I'm on Windows.
I opened it first in CS5, and after font substitution it exported fine, so I figured maybe it was a font problem on your end, but just to be safe I opened it in CS3 to check. Same problem here that you have on your end.
Good news, though. I exported to .inx and opened that. That page opened at 11 inches high, which may be part of the problem, but after resizing, it exported correctly. This is a pretty good inidcator of some minor corruption that is fixable by the export. See Remove minor corruption by exporting

Number format mask of text item is not applied

Hello all,
I want to format a number like 999G999G999G999G990D00
Is specify the format mask under source of the item. But it is not applied and I don't understand why.
See http://apex.oracle.com/pls/otn/f?p=53873:2 for example
Btw. is it possible to set the format for all numbers in the application at once? I want to have a thousand separator in most cases.
Message was edited by:
Jacob_B

Hello Jacob,
Btw. is it possible to set the format for all numbers
in the application at once? I want to have a thousand
separator in most cases.I am using substitution strings for things like that. You can define some "global" substitution strings on page application definition.
So you just have to put in the format (999G999G999G999G990D00 ) in there once and give it a name. Let's say NUMBER_THOUSAND.
Afterwards you can reference it wherever you need the format e.g. this way:
to_char(10000,'&NUMBER_THOUSAND.').
This way you just have one place where to change the format model.
Regards,
Tine

MBean Attribute (Does not apply to application modules)

Can any one tell what this mean ?
MBean Attribute (Does not apply to application modules) :
is this means that it wont help for datasources for any J2EE application ????
Inactive Connection Timeout
The number of inactive seconds on a reserved connection before WebLogic Server reclaims the connection and releases it back into the connection pool.
You can use the Inactive Connection Timeout feature to reclaim leaked connections - connections that were not explicitly closed by the application. Note that this feature is not intended to be used in place of properly closing connections.
When set to 0, the feature is disabled.
MBean Attribute (Does not apply to application modules) :
JDBCConnectionPoolParamsBean.InactiveConnectionTimeoutSeconds
Minimum value: 0
Maximum value: 2147483647

Yes!, they do not apply for any applications they are management interfaces, internal to weblogic.
Below is the brief information about it:
A managed bean (MBean) is a Java bean that provides a Java Management Extensions (JMX) interface. JMX is the J2EE solution for monitoring and managing resources on a network.
BEA WebLogic Server provides a set of MBeans that you can use to configure, monitor, and manage WebLogic Server resources through JMX. This reference document organizes WebLogic Server MBeans into the following categories:
MBeanServer Services, which serve as your entry point into navigating the MBean hierarchies. Some of these MBeans contain attributes and operations for managing changes to WebLogic Server configuration MBeans.
Configuration MBeans, which expose attributes and operations for configuring WebLogic Server resources.
Runtime MBeans, which provide information about the runtime state of its resources.
New MBeans, which have been added in the current release of WebLogic Server. These new MBeans are also listed in other categories in this document (for example, new runtime MBeans are also listed under the Runtime MBeans category).
Deprecated MBeans, which are deprecated in the current release of WebLogic Server.

Selection criteria are not applied to summary fields on group footers.

I wonder if anyone can help me with this problem. I am using Crystal reports version 11.2, and my data source is a Sql Server view.
The records on the view have a date field, and I have selected all records within a given date range in "Selection Formulas".
The records are then grouped, and the Crystal summary facility used to summarise number fields on the group footers.
So for example, if my view contains four records, one with field "amount" = 2, one with field "amount" = 8, one with field "amount" = 6, one with field "amount" = 3, but only the first two records are within the valid date range, you would expect to see the first two records listed out at detail level, then field "amount" summarised at group level, with a summarised value of 10.
ie ....                record1                      2
                       record2                      8
                       group level total         10
This works fine when I run the report using Crystal's "print preview" facility. However, when the report is run from within an application written in C#.NET, the selection criteria are not applied to the summary field, so you get ..
                       record1                      2
                       record2                      8
                       group level total          19
I tried putting the date selection criteria at both record and group level, but that did not work.
I googled the problem and found an article explaining that Crystal first performs the record-level selection, then it creates the groups and totals up any summary fields, and only then does it apply the group-level selection criteria, which can lead to problems like the one I have described above. However, since I have put my date selection criteria at both record and group level, I do not understand why I still get the problem.
In one report I got round this problem by creating a formula that returned zero if the record date was outside of the valid date range, and returned the number field to be summarised if the date was valid, then summarising that formula, instead of summarising the number field directly.
In other reports I created one formula to set a shared variable as zero, then another formula to accumulate it at detail record level, then another formula to display the variable at the group footer. In other words, I did not bother with the Crystal summary facility at all, but created my own summary facility.
While googling the problem to see what other people did in this situation, I noticed that most fixes used variations of the "shared variables and formulae" fix to get round the problem.
The problem is that I have lots of complex reports and it will take ages to replace the summarised fields with shared variables and formulae. The reports were initially tested with "Print Preview" so we did not notice this problem until the C#.Net application was ready to use them. And I can't believe that you are simply meant to ignore the summary facility and re-invent the wheel by doing it all manually.
Please tell me that there is something simple that I have been doing wrong!!! If I have not given enough information for you to answer, please let me know.
Thanks,
Anne-Marie

Hi, Anne-Marie;
You may be running into a common issue that is docuemented here:
[SelectionFormula|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333233303334333833393335%7D.do]
Regards,
Jonathan
Edited by: Jonathan Parminter on Mar 16, 2009 8:03 AM

Why is my CSS style not applied to my HTMLB page ?

Hello !
I'm using a css file to define the layout of my htmlb page... but the layout is not applied.
When I specify the layout CSS in a common html page the layout is applied but not for an htmlb page.
Could someone let me know where I'm wrong ?
EG :
My htmlb page :
<%@page language="abap" %>
<%@extension name="htmlb" prefix="htmlb" %>
<htmlb:content>
<htmlb:page title=" " >
      <html>
            <head>
            <link href="style.css" rel="stylesheet" type="text/css">
            </head>
            <body>
            text1
    <htmlb:form>
        text2
    </htmlb:form>
            </body>
      </html>
</htmlb:page>
</htmlb:content>
My css file style.css :
<%@page language="abap"%>
body {
    background-color: #990000;
    font-family: Verdana;
    font-size: 32x;
    line-height: 32px;
    color: #666666;
As a result, I have a blank page (and not red) with the text "text1" and "text2" written.

This code you have is unfortunately completely bogus. It is just not going to work. Writing HTMLB tags are easy. It takes but minutes to make the magic appear in the browser. But, you have also have to understand a little about what is happening.
At a very first, I would like to recommend this link: <a href="/people/brian.mckellar/blog/2004/06/11/bsp-trouble-shooting-getting-help">Getting Help</a>. You are specifically interested in the section that shows you how to get help about specific tags.
As a next step, look at the help for the <htmlb:page> tag. It is the first important one. See how it is a collection of other <htmlb:document*> tags.
Thereafter, look at SBSPEXT_HTMLB/document.BSP for an example on how to replace the <htmlb:page> sequence in your application.
Once this is done, place you "<link ...>" sequence directly after the <htmlb:headInclude> tag that you have now on your page.
Compile, test, assign 10 points.

Sysprep unattend file not applying when image is captured with wds (no errors)

So I've been around the block a bit using sysprep and wds. Recently I've created a reference image with a virtualbox environment using windows 7 x64. I was succesfully able to create a reference image, sysprep it and capture it to the wds server. My
plan there after was to create driver specific images for each model computer we use here after not having much success using the driver store (another story)
Any how So I take my reference image and deploy it to a new computer... In this case an HP Probook 5310m. Install any missing drivers and Sysprep it with the following command. sysprep /generalize /oobe /unattend:unattend.xml /shutdown
Below is the sysprep file I have been using
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="generalize">
<component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipRearm>0</SkipRearm>
</component>
<component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DoNotCleanUpNonPresentDevices>true</DoNotCleanUpNonPresentDevices>
<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipAutoActivation>true</SkipAutoActivation>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ShowWindowsLive>false</ShowWindowsLive>
<TimeZone>Eastern Standard Time</TimeZone>
<CopyProfile>true</CopyProfile>
<ProductKey>74fdj-7dtw8-q9mp9-ypth8-qb27y</ProductKey>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OEMInformation>
<Logo>c:\windows\system32\oemlogo.bmp</Logo>
<SupportHours>Regular Business Hrs (Overnight Support Provided)</SupportHours>
<SupportURL>url</SupportURL>
<SupportPhone>Phone number</SupportPhone>
</OEMInformation>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
<HideWirelessSetupInOOBE>false</HideWirelessSetupInOOBE>
</OOBE>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>TAAxAEQAMwBzAHQAcgBpACEAUABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</PlainText>
</Password>
<Description>Local Administrator</Description>
<DisplayName>Root</DisplayName>
<Group>Administrators</Group>
<Name>Root</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<TimeZone>Eastern Standard Time</TimeZone>
<ShowWindowsLive>false</ShowWindowsLive>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Order>1</Order>
<CommandLine>slmgr.vbs /ipk {serial key}</CommandLine>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<Order>2</Order>
<CommandLine>slmgr.vbs /ato</CommandLine>
</SynchronousCommand>
</FirstLogonCommands>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<cpi:offlineImage cpi:source="catalog:v:/sources/install_windows 7 professional.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
The machine succesfully syspreps and shuts down. I restart the computer pxe boot and capture the image succesfully.
Now here comes my problem...
Upon deploying the above driver specific image.. my sysprep file is not applied. Nothing from the OOBE wizard answers to the pc logo , or first logon commands are applied ... nothing.. I have gotten no errors during this whole process. I have
started to try to read the logs within the panther folder but havent gotten far.
What is weird to me is that I have tried recreating this image... deploy the reference image... add drivers ... sysprep ...shutdown. And if I boot normally (without capturing the image) the computer shows all of the sysprep changes.. Only when
i capture the image does it not apply the changes....
I'm stumped...
Any ides?

Confirm this scenario: You installed Windows, then ran sysprep and used the /unattend switch. Then you captured the image.
In this scenario there are 2 deployment methods.
1. If you deploy the image with DISM, the answer file generated by sysprep is detected on first boot and settings are applied. It is the same function as if you ran sysprep and chose to restart.
2. If you deploy the image using Setup.exe, it does not use the answer file specified by sysprep prior to capturing. I have not looked into *why* this happens, but I suspect that after the image is applied, it replaces the unattend.xml with the generic one.
If you are using Setup.exe, you need to use its /unattend switch and point to the answer file location. This location cannot be inside of the image. If you are not using setup.exe in a manual method (using WDS) you will need to apply the answer file to the
install image in the WDS snap-in.

MDT 2013: bootstrap.ini not applying username and password for share access

I customized my bootstrap.ini file to skip the welcome screen, set keyboard locale, and enter a service account username and password for share access. The welcome screen skip and keyboard locale work beautifully but it's not applying the share username/password/domain
at all.
bootstrap.ini:
[Settings]
Priority=Default
[Default]
DeployRoot=\\mydeploymentserver\DeploymentShare$
UserID=myuserid
UserDomain=mydomain.com
UserPassword=mypassword
KeyboardLocale=en-US
SkipBDDWelcome=YES
I verified that the unattend.xml file on the MININT volume during deployment had all of this information populated correctly:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ImageInstall>
<OSImage>
<WillShowUI>OnError</WillShowUI>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>2</PartitionID>
</InstallTo>
<InstallFrom>
<Path>\\mydeploymentserver\deploymentshare$\Operating Systems\Windows 7 x64 with District Software - 06222014\Windows 7 x64 with District Software - 06222014.wim</Path>
<MetaData>
<Key>/IMAGE/INDEX</Key>
<Value>1</Value>
</MetaData>
</InstallFrom>
</OSImage>
</ImageInstall>
<Display>
<ColorDepth>16</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<ComplianceCheck>
<DisplayReport>OnError</DisplayReport>
</ComplianceCheck>
<UserData>
<AcceptEula>true</AcceptEula>
</UserData>
</component>
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="generalize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Identification>
<Credentials>
<Username>myusername</Username>
<Domain>mydomain.com</Domain>
<Password>mypassword</Password>
</Credentials>
<JoinDomain>mydomain.com</JoinDomain>
</Identification>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ComputerName>eos-vm-02</ComputerName>
<RegisteredOrganization>Regional School District 19</RegisteredOrganization>
<RegisteredOwner>Information Technology</RegisteredOwner>
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
<TimeZone>Eastern Standard Time</TimeZone>
</component>
<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Home_Page>http://www.eosmith.org</Home_Page>
<DisableWelcomePage>true</DisableWelcomePage>
<DisableFirstRunWizard>false</DisableFirstRunWizard>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Description>EnableAdmin</Description>
<Order>1</Order>
<Path>cmd /c net user Administrator /active:yes</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>UnfilterAdministratorToken</Description>
<Order>2</Order>
<Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>disable user account page</Description>
<Order>3</Order>
<Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
<component name="Microsoft-Windows-TapiSetup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<TapiConfigured>0</TapiConfigured>
<TapiUnattendLocation>
<AreaCode>""</AreaCode>
<CountryOrRegion>1</CountryOrRegion>
<LongDistanceAccess>9</LongDistanceAccess>
<OutsideAccess>9</OutsideAccess>
<PulseOrToneDialing>1</PulseOrToneDialing>
<DisableCallWaiting>""</DisableCallWaiting>
<InternationalCarrierCode>""</InternationalCarrierCode>
<LongDistanceCarrierCode>""</LongDistanceCarrierCode>
<Name>Default</Name>
</TapiUnattendLocation>
</component>
<component name="Microsoft-Windows-SystemRestore-Main" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DisableSR>1</DisableSR>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<UserAccounts>
<AdministratorPassword>
<Value>administratorpassword</Value>
<PlainText>true</PlainText>
</AdministratorPassword>
</UserAccounts>
<AutoLogon>
<Enabled>true</Enabled>
<Username>Administrator</Username>
<Domain>.</Domain>
<Password>
<Value>administratorpassword</Value>
<PlainText>true</PlainText>
</Password>
<LogonCount>999</LogonCount>
</AutoLogon>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>wscript.exe %SystemDrive%\LTIBootstrap.vbs</CommandLine>
<Description>Lite Touch new OS</Description>
<Order>1</Order>
</SynchronousCommand>
</FirstLogonCommands>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<RegisteredOrganization>Regional School District 19</RegisteredOrganization>
<RegisteredOwner>Information Technology</RegisteredOwner>
<TimeZone>Eastern Standard Time</TimeZone>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="offlineServicing">
<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DriverPaths>
<PathAndCredentials wcm:keyValue="1" wcm:action="add">
<Path>\Drivers</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>
</unattend>
... and the bdd.log file appeared not to read the username and password at all:
<![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives = C: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LogPath is now = D:\MININT\SMSOSD\OSDLOGS]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property Debug is now = FALSE]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Cleaned up a dirty deployment.]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives = C: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[No task sequence is in progress.]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Possible OS TargetDisk: \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[GetPartitions: 2]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Possible OS Target Partition: \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Target Partition not big enough: \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Possible OS Target Partition: \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Drive: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found FirstPossibleSystemDrive: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property SMSTSLocalDataDrive is now = D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Unable to connect to BCDStore.]LOG]!><time="05:03:43.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Not running within WinPE or WinRE.]LOG]!><time="05:03:43.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeploymentMethod is now = UNC]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentMethod = UNC]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployRoot is now = X:\Deploy]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Using a local or mapped drive, no connection is required.]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployRoot = X:\Deploy]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = X:]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = X:]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property PHASE is now = PREINSTALL]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeploymentType is now = NEWCOMPUTER]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Phase = PREINSTALL]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[About to run command: wscript.exe "X:\Deploy\Scripts\ZTIGather.wsf" /inifile:Bootstrap.ini]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property inifile is now = Bootstrap.ini]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[------------------------- Object Initialization -------------------------]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[------------------------- Initialization -------------------------]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Synchronizing the environments.]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property DeployRoot is now = X:\Deploy]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property DeployDrive is now = X:]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished synchronizing the environments.]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting OS info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OSCurrentVersion is now = 6.3.9600]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OSCurrentBuild is now = 9600]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OSVersion is now = WinPE]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsServerOS is now = False]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsServerCoreOS is now = False]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting OS info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting HAL information]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property definition is now = BDD_Welcome_ENU.xml]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property HALName is now = acpiapic]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting HAL information]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting network info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Checking network adapter: [00000001] Intel(R) PRO/1000 MT Network Connection]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[MAC address = 00:50:56:85:38:B4]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[IP Address = 172.16.4.182]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[IP Address = fe80::c98:9fef:4305:51f0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Default Gateway = 172.16.4.1]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IPAddress001 is now = 172.16.4.182]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IPAddress002 is now = fe80::c98:9fef:4305:51f0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property MacAddress001 is now = 00:50:56:85:38:B4]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property DefaultGateway001 is now = 172.16.4.1]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting network info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting DP info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Unable to determine ConfigMgr distribution point]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting DP info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting WDS server info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Not Wizard = False]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property WizardComplete is now = N]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property WDSServer is now = mydeploymentserver.mydomain.com]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting WDS server info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property HostName is now = MININT-U1TGFAD]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting asset info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[FindFile: The file x86\Microsoft.BDD.Utility.dll could not be found in any standard locations.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[FindFile(...\Microsoft.BDD.Utility.dll) Result : 1]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[RUN: regsvr32.exe /s ""]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[FindFile(...\Microsoft.BDD.Utility.dll) Result : 0]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[RUN: regsvr32.exe /s "X:\Deploy\Tools\x64\Microsoft.BDD.Utility.dll"]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property AssetTag is now = No Asset Tag]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SerialNumber is now = VMware-42 05 2b f7 cd 5b 63 fd-83 8a 77 84 7c ed 79 05]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Make is now = VMware, Inc.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Model is now = VMware Virtual Platform]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Product is now = 440BX Desktop Reference Platform]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property UUID is now = F72B0542-5BCD-FD63-838A-77847CED7905]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Memory is now = 2047]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Architecture is now = X64]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property ProcessorSpeed is now = 2800]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property CapableArchitecture is now = AMD64 X64 X86]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsLaptop is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsDesktop is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsServer is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsUEFI is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsOnBattery is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsX86 is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsX64 is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsSLAT is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting asset info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting OS SKU info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Unable to determine Windows SKU while in Windows PE.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Determining the Disk and Partition Number from the Logical Drive X:\WINDOWS]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OriginalArchitecture is now = ]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OriginalArchitecture is now = ]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OriginalArchitecture is now = ]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting virtualization info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsHypervisorRunning is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsVT is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsNX is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Supports64Bit is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsHyperVRole is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsVM is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property VMPlatform is now = VMware]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting virtualization info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Connection succeeded to MicrosoftVolumeEncryption]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[There are no encrypted drives]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsBDE is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Processing the PREINSTALL phase.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Determining the INI file to use.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished determining the INI file to use.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Using from [Settings]: Rule Priority = DEFAULT]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[------ Processing the [DEFAULT] section ------]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property DEPLOYROOT is now = \\mydeploymentserver\DeploymentShare$]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Using from [DEFAULT]: DEPLOYROOT = \\mydeploymentserver\DeploymentShare$]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[------ Done processing X:\Deploy\Scripts\Bootstrap.ini ------]LOG]!>

Basics - Server 2008 R2 - SP1, WDS, MDT 2013
Well all, I've done this at least 20 times today and the deployment share info is still wrong...
Someone else built and messed with this thing so i'm trying to fix it. We have 2 MDT servers and 1 WDS that is on the Production MDT. I've turned the test MDT off.
It was working fine, until I updated the deployment share ... after adding some drivers for the surface pro 3 for the pxe boot
Very Simple bootstrap.ini
[Settings]
Priority=Default
[Default]
DeployRoot=\\MMPDEPLOY02\DeploymentShare$
UserID=xxx
UserDomain=xxx
UserPassword=xxx
KeyboardLocale=en-US
SkipBDDWelcome=YES
It continues to show up on the client as ||mdt901w8|deploymentshare$ (test server) (pipes for \ since it makes it a link and i'm new)
I've deleted all the .wim and associated files from all locations from the deployment share\boot folder and from the wds remote install\boot\x64\images folder where they are instead of the remote install\boot\images folder that everyone refers to.
I really can't figure this one out... I know it's something simple I'm over looking but I can't see it..
Any ideas..

I have two faults! 1, an error comes up in Ps CC 2014 "could not apply the saved panel configuration, restring to default and my tools have disappeared completely and anything ive tried I cannot get them back not even the drop down menu in 'window' helps

I have two faults! 1, an error comes up in Ps CC 2014 "could not apply the saved panel configuration, restring to default and my tools have disappeared completely and anything ive tried I cannot get them back not even the drop down menu in 'window' helps at all. And 2, Lr everytime I load it up it gives me the option to retry or switch to and it takes a while for me to even get anywhere with it I think it has something to do with the catalogs? I've been using these programs for a few years now on a Mac...no problem but when I use a PC when I'm away coz it's the (only) comp available these happen PC's are so useless! Please can anyone help??...

I can give a few suggestions on Photoshop CC 2014, but Lightroom is a separate forum and you should ask Lr questions there.
First close Photoshop.
Then start Photoshop by double-clicking on it's icon and very quickly after that, hold down the ctrl-alt-shift keys until you see the reset dialog. answer "Yes" to delete settings, and let Photoshop continue to load.
It's tricky to do and may take a few tries, but at least it should reset Photoshop CC 2014 to defaults.
Gene

ACR not applying linear segment w/ProPhoto

Similar Messages

Maybe you are looking for