Log clean up ?

is it safe to delete the old log files in these directories?
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs
thanks
David Ulrich

yes, though by default Exchange should be aging out old ones every 30 days.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

  • Log cleaning takes a lot

    Hi,
    I've been reading the forum but could not find a hint for solving my problem. I apologize if I missed something and the answer is already there.
    My scenario for using BDB (je-4.0.103):
    - a read-only environment with about 4000 databases. The environment uses about 100GB disk space. Log file size is 10MB. Cache size is 100MB.
    - databases are opened only when needed and are closed after a few minutes of inactivity
    - when in read-only mode cleaner, checkpointer and IN compressor threads are disabled
    - once a day, the env is closed and re-opened in read/write mode for performing bulk data load, in deferred write mode, without transactions. About 0.5 - 1GB of data is imported daily (1 million key-value pairs).
    - during load, IN compressor is enabled but cleaner and checkpointer are not
    - log cleaning and checkpointing is invoked manually at the end of data import using the algorithm suggested in the docs
    After several months of working properly without any signs of degradation the whole thing broke down suddenly. The log cleaning takes now hours instead of minutes and it does not seem to do its job: the environment is now 250GB and keeps growing. Restart also takes several hours.
    Any help would be appreciated. If more details about my setup is needed, I can provide it.
    Thank you!
    Edited by: user9045772 on Sep 17, 2010 3:30 AM
    Mentioned the size of the cache.

    Hi Eric,
    Thank you very much for your help.
    I just tried increasing the cache from 100MB to 1GB and it made miracles. Log cleaning was finally completed after 2 hours. The db start time is now back to normal (less than 2 minutes).
    I'm still concerned with the fact that log cleaning takes a lot, but at least it finishes after several hours. Will have a look at db space utilization after completing a new run and will tell you the results.
    Until then, here are the env config and stats (after increasing the cache), maybe you spot something odd:
    ------------------ Env Config ------------------------------------
    allowCreate=true
    cacheSize=1048576000
    txnNoSync=false
    txnWriteNoSync=false
    {je.log.fileMax=10485760,
    je.env.runCheckpointer=false,
    je.env.runCleaner=false,
    je.log.totalBufferBytes=10485760,
    je.cleaner.minFileUtilization=50,
    je.env.isLocking=false,
    je.cleaner.minUtilization=80,
    je.sharedCache=true,
    je.env.runINCompressor=true,
    je.env.isTransactional=false,
    je.env.isReadOnly=false,
    je.log.faultReadSize=120960,
    je.log.bufferSize=5242880,
    je.maxMemory=10485760000,
    je.log.numBuffers=2,
    je.log.iteratorReadSize=120960}
    ------------------ Env Stats ------------------------------------
    I/O: Log file opens, fsyncs, reads, writes, cache misses.
         bufferBytes=10,485,760
         endOfLog=0x0/0x0
         nBytesReadFromWriteQueue=0
         nBytesWrittenFromWriteQueue=0
         nCacheMiss=24,646
         nFSyncRequests=1
         nFSyncTimeouts=0
         nFSyncs=1
         nFileOpens=5,319
         nLogBuffers=2
         nLogFSyncs=3
         nNotResident=24,646
         nOpenFiles=100
         nRandomReadBytes=1,664,658,816
         nRandomReads=13,751
         nRandomWriteBytes=2,961,648
         nRandomWrites=1
         nReadsFromWriteQueue=0
         nRepeatFaultReads=2
         nSequentialReadBytes=53,787,475,644
         nSequentialReads=274,985
         nSequentialWriteBytes=0
         nSequentialWrites=0
         nTempBufferWrites=0
         nWriteQueueOverflow=0
         nWriteQueueOverflowFailures=0
         nWritesFromWriteQueue=0
    Cache: Current size, allocations, and eviction activity.
         adminBytes=4,807,377
         cacheTotalBytes=21,728,916
         dataBytes=6,435,779
         lockBytes=0
         nBINsEvictedCACHEMODE=0
         nBINsEvictedCRITICAL=0
         nBINsEvictedEVICTORTHREAD=0
         nBINsEvictedMANUAL=0
         nBINsFetch=53,566
         nBINsFetchMiss=543
         nBINsStripped=0
         nEvictPasses=0
         nLNsFetch=90,991
         nLNsFetchMiss=24,096
         nNodesEvicted=0
         nNodesScanned=0
         nNodesSelected=0
         nRootNodesEvicted=0
         nSharedCacheEnvironments=1
         nUpperINsEvictedCACHEMODE=0
         nUpperINsEvictedCRITICAL=0
         nUpperINsEvictedEVICTORTHREAD=0
         nUpperINsEvictedMANUAL=0
         nUpperINsFetch=36,940
         nUpperINsFetchMiss=9
         requiredEvictBytes=0
         sharedCacheTotalBytes=21,728,916
    Cleaning: Frequency and extent of log file cleaning activity.
         cleanerBackLog=7,441
         fileDeletionBacklog=0
         nCleanerDeletions=0
         nCleanerEntriesRead=1,400,054
         nCleanerRuns=4,845
         nClusterLNsProcessed=0
         nINsCleaned=0
         nINsDead=0
         nINsMigrated=0
         nINsObsolete=86
         nLNQueueHits=0
         nLNsCleaned=0
         nLNsDead=0
         nLNsLocked=0
         nLNsMarked=0
         nLNsMigrated=0
         nLNsObsolete=1,390,901
         nMarkLNsProcessed=0
         nPendingLNsLocked=0
         nPendingLNsProcessed=0
         nRepeatIteratorReads=0
         nToBeCleanedLNsProcessed=0
         totalLogSize=0
    Node Compression: Removal and compression of internal btree nodes.
         cursorsBins=0
         dbClosedBins=0
         inCompQueueSize=0
         nonEmptyBins=0
         processedBins=15
         splitBins=0
    Checkpoints: Frequency and extent of checkpointing activity.
         lastCheckpointEnd=0xae0c/0x74f5c6
         lastCheckpointId=1,590
         lastCheckpointStart=0xae0c/0x4c6dea
         nCheckpoints=1
         nDeltaINFlush=15
         nFullBINFlush=47
         nFullINFlush=51
    Environment: General environment wide statistics.
         btreeRelatchesRequired=148
    Locks: Locks held by data operations, latching contention on lock table.
         nLatchAcquireNoWaitUnsuccessful=0
         nLatchAcquiresNoWaitSuccessful=0
         nLatchAcquiresNoWaiters=0
         nLatchAcquiresSelfOwned=0
         nLatchAcquiresWithContention=0
         nLatchReleases=0
         nRequests=0
         nWaits=0
    Edited by: user9045772 on Sep 17, 2010 4:12 AM
    added env config and stats

  • Pacman log cleaner

    I've written a script to clean up the pacman log file. (It was 32 MB on my system, mostly because Sage was built in the post_install function and thus spammed the log file.)
    I've posted it on my site along with an explanation of what it does. (I've added syntax highlighting to my toolchain and wanted an excuse to use it. )
    Last edited by Xyne (2010-05-06 12:33:09)

    Hehe I wrote something similar to this one for myself a few days ago. It cleans the pacman.log of spam as "Synchronizing package databases..." and "Starting full system upgrade..." lines.
    If anyone wants it, here it is...(author of the thread, if you find my post appropriate, please contact me or write here, and I will remove this code. )
    sudo pacman -Syu &&
    sudo sed -i '/starting full system upgrade/ d' /var/log/pacman.log &&
    sudo sed -i '/synchronizing package lists/ d' /var/log/pacman.log &&
    echo "==> log file cleared of spam messages" &&
    echo "==> exit" &&
    date +'%A, %d.%m.%y., %k:%M' > /home/<YOUR_USER_HERE>/.scripts/synched # or whatever you like
    The last line is to keep track of when pacman was last synched.
    Cheers.

  • Log file cleaning problem

    Hi,
    I'm evaluating Berkeley DB Java Edition for my application, and I have the following code:
    public class JETest {
         private Environment env;
         private Database myDb;
         public JETest() throws DatabaseException {
              EnvironmentConfig envConfig = new EnvironmentConfig();
              envConfig.setAllowCreate(true);
              envConfig.setTransactional(false);
              envConfig.setCachePercent(1);
              env = new Environment(new File("/tmp/test2"),envConfig);
              DatabaseConfig dbConfig = new DatabaseConfig();
              dbConfig.setDeferredWrite(true);
              dbConfig.setAllowCreate(true);
              dbConfig.setTransactional(false);
              myDb = env.openDatabase(null, "testing", dbConfig);
         public void cleanup() throws Exception {
              myDb.close();
              env.close();
         private void insertDelete() throws DatabaseException {
              int keyGen = Integer.MIN_VALUE;
              byte[] key = new byte[4];
              byte[] data = new byte[1024];
              ByteBuffer buff = ByteBuffer.wrap(key);
              for (int i=0;i<20000;i++) {
                   buff.rewind();
                   buff.putInt(keyGen++);
                   myDb.put(null, new DatabaseEntry(key), new DatabaseEntry(data));
              int count = 0;
              System.out.println("done inserting");
              keyGen = Integer.MIN_VALUE;
    OperationStatus status;
              for (int i=0;i<20000; i++) {
                   buff.rewind();
                   buff.putInt(keyGen++);
                   count++;
                   status = myDb.delete(null, new DatabaseEntry(key));
    if (status != OperationStatus.SUCCESS) {
                        System.out.println("Delete failed.");
              System.out.println("called delete "+count+" times");
              env.sync();
         public static void main(String[] args) throws Exception {
              JETest test = new JETest();
              test.insertDelete();
              test.cleanup();
    After running the above, I expected that the log file utilization be 0%, because I delete each and every record in the database. The status returned by the delete() method was OperationStatus.SUCCESS for all the invocations.
    I ran the DbSpace utility, and this is what I found:
    $ java -cp je-3.2.13/lib/je-3.2.13.jar com.sleepycat.je.util.DbSpace -h /tmp/test2 -d
    File Size (KB) % Used
    00000000 9765 99
    00000001 3236 99
    TOTALS 13001 99
    Obviously, the cleaner thread won't clean log files that are 99% used.
    I did expect the logs to be completely empty, though. What is going on here?
    Thanks,
    Lior

    Lior,
    With the default heap size (64m) I was able to reproduce the problem you're seeing. I think I understand what's happening.
    First see this note in the javadoc for setDeferredWrite:
    http://www.oracle.com/technology/documentation/berkeley-db/je/java/com/sleepycat/je/DatabaseConfig.html#setDeferredWrite(boolean)
    Note that although deferred write databases can page to disk if the cache is not large enough to hold the databases, they are much more efficient if the database remains in memory. See the JE FAQ on the Oracle Technology Network site for information on how to estimate the cache size needed by a given database. In the current implementation, a deferred write database which is synced or pages to the disk may also add additional log cleaner overhead to the environment. See the je.deferredWrite.temp property in <JEHOME>/example.properties for tuning information on how to ameliorate this cost.
    The statement above about "additional log cleaner overhead" is not quite accurate. Specifically, we do not currently keep track of obsolete information about DW (Deferred Write) databases. We are considering improvements in this area.
    Your test has brought out this issue to an extreme degree because of the very small cache size, and the fact that you delete all records. Most usage of DW that we see involves a bulk data load (no deletes), or deletes performed in memory so the record never goes to disk at all. With the tiny cache in your test, the records do go to disk before they are deleted.
    You can avoid this situation in a couple of different ways:
    1) Use a larger cache. If you insert and delete before calling sync, the inserted records will never be written to disk.
    2) If this is a temporary database (no durability is required), then you can set the je.deferredWrite.temp configuration parameter mentioned above. Setting this to true enables accurate utilization tracking for a DW database, for the case where durability is not required.
    # If true, assume that deferred write database will never be
    # used after an environment is closed. This permits a more efficient
    # form of logging of deferred write objects that overflow to disk
    # through cache eviction or Database.sync() and reduces log cleaner
    # overhead.
    # je.deferredWrite.temp=false
    # (mutable at run time: false)
    Will either of these options work for your application?
    Mark

  • Does cleaning sort records and impact on max log size

    I'm looking for confirmation that the act of cleaning logs produces sorted records, equivalent to having inserted them in sorted order to begin with. If that is the case is the memory overhead of cleaning proportional to the maximum log file size, or will it spill to disk to sort? I ask since the max log file size is 1G, and if there is a memory component then it may be relevant to take into consideration.
    On a similar note, is increasing the log file size from 10MB recommended if the database is large (say a TB)? Are there some linear operations (most likely in the admin/maintenance category) that have to iterate over each log file?
    Thanks.

    Hi,
    I'm looking for confirmation that the act of cleaning logs produces sorted records, equivalent to having inserted them in sorted order to begin with.No, that's not exactly true. When records are written (migrated to the end of the log) during the log cleaning process, any clustering (writing of adjacent records in key order) occurs on a per BIN (bottom internal node) basis. So at most 128 records (or DatabaseConfig.setNodeMaxEntries) with adjacent key values are sorted and written out together in this manner. But normally not all records in a BIN will be migrated and I'll describe more about this below.
    If that is the case is the memory overhead of cleaning proportional to the maximum log file size, or will it spill to disk to sort? I ask since the max log file size is 1G, and if there is a memory component then it may be relevant to take into consideration.No, the memory used for sorting in this case is the JE cache itself -- the memory that holds the Btree. The log cleaner thread moves records to be migrated into the Btree (in the cache), and flags them for migration. These records are written lazily the next time their parent Btree node (the BIN I mentioned) needs to be flushed. This can occur for two reasons: 1) when the BIN is evicted from the cache because the cache is full, or 2) during the next checkpoint, since a checkpoint will flush all dirty BINs. The most desirable situation is that the BIN is flushed during the checkpoint, not during eviction, to reduce the number of times that a single BIN is flushed to disk. If a BIN is evicted, it may have to be fetched again later in order to migrate more records as part of the log cleaning process, and this is counterproductive.
    So during this process, the number of records that are written to disk in key order in a cluster, such that they are physically adjacent on disk, is variable. It depends on how many records are processed by cleaner threads, and inserted in their parent BIN for migration, between checkpoint intervals, and whether the BINs are evicted during this period.
    A physical cluster of records includes the BIN itself as well as its child records that are migrated for log cleaning. The fact that the BIN is part of the cluster is beneficial to apps where not all BINs fit in the cache. If a record and its parent BIN are not in cache, and the app reads that record, the BIN and the record must both be fetched from disk. Since they will be in physical proximity to each other on disk, disk head movement is avoided or reduced.
    However, not all of the child records in a BIN will necessarily be part of a physical cluster. If only some of the records in a BIN were processed by the log cleaner before the BIN is flushed by the checkpointer or evictor, then only a subset of the child records will be written as part of the cluster. In other words, even for a single BIN, all the child records in that BIN are not normally written out together in a cluster.
    Clustering is a useful feature and something we would like to enhance in the future. What I've described above is as far as we've gotten with this feature in the currently released and supported product. However, there are two experimental configuration settings that cause additional clustering to occur. These cause additional records to be written to disk when their parent BIN is flushed. If you're interested in trying these, I will be happy to explain them and work with you. But you should be aware that they're not currently in the standard, supported set of features, and are not well tested.
    I'm not sure whether I've given you less information than you need or more than you wanted. :-) If you describe in detail what you're trying to do, and more about your app and performance requirements, I may be able to offer more concrete advice.
    On a similar note, is increasing the log file size from 10MB recommended if the database is large (say a TB)? Are there some linear operations (most likely in the admin/maintenance category) that have to iterate over each log file?Yes, there are such operations and per-log file overhead, and we recommend using using a 20M to 50M log file size for large data sets. Log files larger than 50MB could decrease log cleaner performance.
    --mark                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Empty file not cleaned out by the cleaner

    Another day, another post about cleaner. Let me describe a problem on this sample dataset I have.
    I have a small BDB with the following 4 files
    -rw-rw-r-- 1 apps apps 34M Jul 18 21:58 00000061.jdb
    -rw-rw-r-- 1 apps apps 53K Jul 18 22:00 00000062.jdb
    -rw-rw-r-- 1 apps apps 34M Jul 18 22:00 00000063.jdb
    -rw-rw-r-- 1 apps apps 664K Aug 1 00:22 00000064.jdb
    When I run DBSpace on it, it reports this
    File 0x61: <summary totalCount="1" totalSize="35022741" totalINCount="0" totalINSize="0" totalLNCount="1" totalLNSize="35022741" obsoleteINCount="0" obsoleteLNCount="1" obsoleteLNSize="35022741" obsoleteLNSizeCounted="1"/>
    Recalculated File 0x61: <summary totalCount="1" totalSize="35022741" totalINCount="0" totalINSize="0" totalLNCount="1" totalLNSize="35022741" obsoleteINCount="0" obsoleteLNCount="1" obsoleteLNSize="0" obsoleteLNSizeCounted="0"/><extended-info recalcObosleteINSize="0" recalcObosletedLNSize="35022741"/>
    File 0x62: <summary totalCount="52" totalSize="53253" totalINCount="9" totalINSize="1493" totalLNCount="27" totalLNSize="50211" obsoleteINCount="9" obsoleteLNCount="23" obsoleteLNSize="1556" obsoleteLNSizeCounted="23"/>
    Recalculated File 0x62: <summary totalCount="52" totalSize="53253" totalINCount="9" totalINSize="1493" totalLNCount="27" totalLNSize="50211" obsoleteINCount="9" obsoleteLNCount="23" obsoleteLNSize="0" obsoleteLNSizeCounted="0"/><extended-info recalcObosleteINSize="1493" recalcObosletedLNSize="1556"/>
    File 0x63: <summary totalCount="1" totalSize="35603241" totalINCount="0" totalINSize="0" totalLNCount="1" totalLNSize="35603241" obsoleteINCount="0" obsoleteLNCount="0" obsoleteLNSize="0" obsoleteLNSizeCounted="0"/>
    Recalculated File 0x63: <summary totalCount="1" totalSize="35603241" totalINCount="0" totalINSize="0" totalLNCount="1" totalLNSize="35603241" obsoleteINCount="0" obsoleteLNCount="0" obsoleteLNSize="0" obsoleteLNSizeCounted="0"/><extended-info recalcObosleteINSize="0" recalcObosletedLNSize="0"/>
    File 0x64: <summary totalCount="521" totalSize="689233" totalINCount="115" totalINSize="24425" totalLNCount="165" totalLNSize="646260" obsoleteINCount="107" obsoleteLNCount="79" obsoleteLNSize="5132" obsoleteLNSizeCounted="79"/>
    Recalculated File 0x64: <summary totalCount="521" totalSize="689233" totalINCount="115" totalINSize="24425" totalLNCount="165" totalLNSize="646260" obsoleteINCount="107" obsoleteLNCount="79" obsoleteLNSize="0" obsoleteLNSizeCounted="0"/><extended-info recalcObosleteINSize="22468" recalcObosletedLNSize="5132"/>
    File Size (KB) % Used % Used (recalculated)
    00000061 34201 0 0
    00000062 52 91 91
    00000064 673 93 93
    00000063 34768 100 100
    TOTALS 69695 50 50
    To me this looks like file 61 could be compacted out.
    In a separate program, I try to clean/compact it.
                   props.put("je.log.fileMax", "1000000");
                   props.put("je.cleaner.minUtilization", "90");
                   props.put("je.cleaner.minFileUtilization", "5");
                   props.put("je.cleaner.minAge", "1");
                   props.put("je.cleaner.readSize", "64000000");
                   props.put("je.cleaner.lookAheadCacheSize", "64000");
                   props.put("je.maxMemory", "64000000");
    followed by open and do something like this
    boolean anyCleaned = false;
    while (bdbEnv.cleanLog() > 0) {
    anyCleaned = true;
    if (anyCleaned) {
    CheckpointConfig force = new CheckpointConfig();
    force.setForce(true);
    bdbEnv.checkpoint(force);
    cleanLog() does not indicate that anything can be cleaned.
    If I force it with this property (bad practice), it does clean up and create 2 nicely compacted 30M files.
    props.put("je.cleaner.forceCleanFiles", "0-1000");
    I have the following questions
    1) How can I get it to clean without forcing it? I am okay with extra resources to be used in cleaning it, because we have a set of files produced every hour that we never write to again, so once they are produced, I can spend some time on compacting/cleaning them for good. I can see that we are using 50% more space here, and that would be fine, but I did specify je.cleaner.minFileUtilization to be 5% so empty files should be removed.
    2) I also thought that setting je.log.fileMax would create files that are no more than 10M, but I am getting files that are 33M for some reason. The BDBs were created using same set of parameters.
    We are using 3.3.75 version. There is a newer version, but release notes do not make me think that this is going to be affected.
    P.S. We actually have a support contract, but I thought I'd post here first. We use BDB quite a lot in our large scale distributed system.
    -Emile

    Emile and I resolved this over email and I'd like to let everyone else know what happened, for the record and in case you run into it.
    This is a case where there is only one JE log file that has low utilization and needs cleaning -- all other log files have high utilization. A separate program is run that calls Environment.cleanLog and checkpoint in order to force the cleaning to occur. It closes the environment immediately after performing the cleaning.
    Here's what happened. File 61 is the file that needs cleaning.
    1. When the environment is opened, the built-in log cleaner daemon thread starts. It determines that log cleaning is needed, so it selects file 61 and starts cleaning it.
    2. Then the app calls cleanLog, which returns 0 because there are no files to be cleaned. File 61 is already being cleaned by the daemon thread.
    3. The app very quickly finishes and closes the environment, which aborts any log cleaning that is in progress. The cleaning of file 61 in the daemon thread is aborted.
    This is solved by disabling the cleaner daemon thread during the batch cleaning process. This is done by setting
    je.env.runCleaner=false
    in je.properties. You can also use EnviornmentConfig.ENV_RUN_CLEANER with EnvironmentConfig.setConfigParam.
    We'll add a note to the documentation of the cleanLog method about this.
    Emile, thanks for reporting this and working with me on it.
    --mark                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • How to get the cleaner thread to run

    Hi,
    I googled documentation/ previous posts, but the topic about getting the log files cleaned is still unclear to me.
    I have created around 24000 records and then deleted all of them ( ie., there is'nt even a single active record in the database). However, the folder size (around 35MB) just wont go down. Google pointed out that this should be taken care of by cleaner thread.
    I have'nt written any code/properties specific to cleaner thread, nor any other properties to do with diskspace etc. So I assume everything is default.
    Would this be run automatically ( assuming even a single record is'nt actually active) or do I need to do something to actually reclaim the diskspace?
    There is limited disk space on this folder for me and I expected the delete to actually delete and make the disk space available immediately (or soon after).
    Any help is greatly appreciated.
    Thanks.

    Cleaning and checkpointing occur in background, asynchronously, and are driven by writes to the log.
    In your test, you insert a bunch of records, then delete them all, then stop. Who knows whether log cleaning and a checkpoint happened to occur after you did the deletions. Probably not. You need to keep the app running and writing data.
    Please do this test: Alternate insertions, then deletions, then insertions, then deletions, etc. Keep this running. You'll see the cleaner deleting the old files.
    --mark                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Confused about the log files

    I have written an application that has a Primary and Secondary database. The application creates tens-of-thousands of records in the Primary database, with a 1-to-1 relationship in the Secondary. On subsequent runs it will either update existing Primary records (which should not update the secondary as that element does not change) or it will create new records.
    The application actually works correctly, with the right data, the right updates and the right logical processing. The problem is the log files.
    The input data I am testing with is originally 2Mb as a CSV file and with a fresh database it creates almost 20Mb of data. This is about right for the way it splits the information up and indexes it. If I run the application again with exactly the same data, it should just update all the entries and create nothing new. My understanding is that the updated records will be written to the end of the logs, and the old ones in the earlier logs would be redundant and the cleaner thread would clean them up. I am explicitly cleaning as per the examples. The issue is that each run, the data just doubles in size! Logically it is fine, physically it is taking a ridiculous amount of space. RUnning DbSpace shows that the logs are mostly full (over 90%) where I would expect most to be empty, or sparsely occupied as the new updates are written to new files. cleanLog() does nothing. I am at a total loss!
    Generally the processing I am doing on the primary is looking up the key, if it is there updating the entry, if not creating one. I have been using a cursor to do this, and using the putCurrent() method for existing updates, and put() for new records. I have even tried using Database.delete() and the full put() in place of putCurrent() - but no difference (except it is slower).
    Please help - it is driving me nuts!

    Let me provide a little more context for the questions I was asking. If this doesn't lead us further into understanding your log situation, perhaps we should take this offline. When log cleaning doesn't occur, the basic questions are:
    a. is the application doing anything that prohibits log cleaning? (in your case, no)
    b. has the utilization level fallen to the point where log cleaning should occur? (not on the second run, but it should on following runs)
    c. does the log utilization level match what the application expects? (no, it doesn't match what you expect).
    1) Ran DbDump with and withour -r. I am expecting the
    data to stay consistent. So, after the first run it
    creates the data, and leaves 20mb in place, 3 log
    files near 100% used. After the second run it should
    update the records (which it does from the
    applications point of view) but I now have 40mb
    across 5 log files all near 100% usage.I think that it's accurate to say that both of us are not surprised that the second run (which updates data but does not change the number of records) creates a second 20MB of log, for a total of 40MB. What we do expect though, is that the utilization reported by DbSpace should fall to closer to 50%. Note that since JE's default minimum utilization level is 50%, we don't expect any automatic log cleaning even after the second run.
    Here's the sort of behavior we'd expect from JE if all the basics are taken care of (there are enough log files, there are no open txns, the application stays up long enough for the daemon to run, or the application does batch cleanLog calls itself, etc).
    run 1 - creates 20MB of log file, near 100% utilization, no log cleaning
    run 2 - updates every record, creates another 20MB of log file, utilization falls, maybe to around 60%. No log cleaning yet, because the utilization is still above the 50% threshold.
    run 3 - updates every record, creates another 20MB of log file, utilization falls below 50%, log cleaning starts running, either in the background by the daemon thread, or because the app calls Environment.cleanLog(), without any need to set je.cleaner.forceCleanFiles.
    So the question here is (c) from above -- you're saying that your DbSpace utilization level doesn't match what you believe your application is doing. There are three possible answers -- your application has a bug :-), or with secondaries and whatnot, JE is representing your data in a fashion you didn't expect, or JE's disk space utilization calculation is inaccurate.
    I suggested using DbDump -r as a first sanity check of what data your application holds. It will dump all the valid records in the environment (though not in key order, no -r is slower, but dumps in key order). Keys and data should up on different lines, so the number of lines in the dump files should be twice the number of records in the environment. You've done this already in your application, but this is an independent way of checking. It also makes it easier to see what portion of data is in primary versus secondary databases, because the data is dumped into per-database files. You could also load the data into a new, blank environment to look at it.
    I think asked you about the size of your records because a customer recently reported a JE disk utilization bug, which we are currently working on. It turns out that if your data records are very different in size (in this case, 4 orders of magnitude) and consistently only the larger or the smaller records are made obsolete, the utilization number gets out of whack. It doesn't really sound like your situation, because you're updating all your records, and they don't sound like they're that different in size. But nevertheless, here's a way of looking at what JE thinks your record sizes are. Run this command:
    java -jar je.jar DbPrintLog -h <envhome> -S
    and you'll see some output that talks about different types of log entries, and their sizes. Look at the lines that say LN and LN_TX at the top. These are data records. Do they match the sizes you expect? These lines do include JE's per-record headers. How large that is depends on whether your data is transactional or not. Non-transactional data records have a header of about 35 bytes, whereas transactional data records have 60 bytes added to them. If your data is small, that can be quite a large percentage. This is quite a lot more than for BDB (Core), partly because BDB (Core) doesn't have record level locking, and partly because we store a number of internal fields as 64 bit rather than 16 or 32 bit values.
    The line that's labelled "key/data" shows what portion JE thinks is the application's data. Note that DbPrintLog, unlike DbSpace, doesn't account for obsoleteness, so while you'll see a more detailed picture of what the records look like in the log, you may see more records than you expect.
    A last step we can take is to send you a development version of DbSpace that has a new feature to recalculate the utilization level. It runs more slowly than the vanilla DbSpace, but is a way of double checking the utilization level.
    In my first response, I suggested trying je.cleaner.forceCleanFiles just to make it clear that the cleaner will run, and to see if the problem is really around the question of what the utilization level should be. Setting that property lets the cleaner bypass the utilization trigger. If using it really reduced the size of your logs, it reinforces that your idea of what your application is doing is correct, and casts suspicion on the utilization calculation.
    So in summary, let's try these steps
    - use DbDump and DbPrintLog to double check the amount and size of your application data
    - make a table of runs, that shows the log size in bytes, number of log files, and the utilization level reported by DbSpace
    - run a je.cleaner.forceCleanFiles cleanLog loop on one of the logs that seems to have a high utilization level, and see how much it reduces to, and what the resulting utilization level is
    If it all points to JE, we'll probably take it offline, and ask for your test case.
    Regards,
    Linda

  • Lost calls from the call log

    I have had a E90 now for more then a year and have been very happy with the phone/gps/camera oh whatever you want to call it except for 1 thing.
    It seems like the call logs clean themselves out. Initially I was told that it was a problem with the firmware but they have updated the firmware and I still have the problem. As it is if somebody calls me I maybe able to see the number in the incoming call log for a day or maybe 2 or sometime only an hour. I always thought that the outgoing log would store the last 20 dialed numbers and the last 10 incoming and missed calls but not on mine. If I call many numbers in a single day I may see up to 7 and in the receive log as much as 4 but then for no reason I would suddenly have an empty set of logs.
    Any idea how to fix that? I am on the latest firmware that shipped in Sept 2008.
    Thanks in advance

    Yes, on the device select the number you want to add, then in the bottom left on your key board press the menu button. Then tap on add contact and you should get a pop up to add the phone number to a contact as a new, add to existing, or cancel.

  • Appfirewall.log dies daily

    Yes, literally daily. Logging to /private/var/log/appfirewall.log works perfectly until the daily log clean-up kicks in at 03:15 every morning. Thereafter the appfirewall.log displays no new entries.
    The only way I've got to get it start logging again is to reboot, which is not good, or disabling and re-enabling the firewall, which is annoying.
    Can anyone suggest a resolution to this?
    Message was edited by: Jay from BKK

    In regards to the firewall messages you're noticing in your log, I'm having the same issue.
    I'm on a 10.10.x.x private network and I'm also getting connection attempts from a 209.85.x.x IP. Specifically, my requests are originating from 209.85.225.102.
    I can't figure out how a request from an IP in this subnet would get behind our NAT, which leads me to believe that a Windows PC on our network has been compromised and is sending out spoofed packets. Since I can't identify the machine by its IP, I haven't yet figured out which machine it is.

  • ClamAV fails to scan for viruses in emails [CLAWS MAIL]

    I've recently switched from Thunderbird to Claws Mail and ran into one small, but annoying, problem.
    I want to use ClamAV + the clamav extension for claws mail to scan for viruses, however it does seem to have permission problems.
    clamd is running, user and group clamav all have the relevant permissions as far as I can tell, however upon scanning my mail, I always end up with the following error:
    Scanning error:
    /home/username/.claws-mail/mimetmp/0000000e.mimetmp: lstat() failed: Permission denied. ERROR
    Here's my clamd.conf:
    ## Please read the clamd.conf(5) manual before editing this file.
    # Comment or remove the line below.
    #Example
    # Uncomment this option to enable logging.
    # LogFile must be writable for the user running daemon.
    # A full path is required.
    # Default: disabled
    LogFile /var/log/clamav/clamd.log
    # By default the log file is locked for writing - the lock protects against
    # running clamd multiple times (if want to run another clamd, please
    # copy the configuration file, change the LogFile variable, and run
    # the daemon with --config-file option).
    # This option disables log file locking.
    # Default: no
    #LogFileUnlock yes
    # Maximum size of the log file.
    # Value of 0 disables the limit.
    # You may use 'M' or 'm' for megabytes (1M = 1m = 1048576 bytes)
    # and 'K' or 'k' for kilobytes (1K = 1k = 1024 bytes). To specify the size
    # in bytes just don't use modifiers.
    # Default: 1M
    #LogFileMaxSize 2M
    # Log time with each message.
    # Default: no
    LogTime yes
    # Also log clean files. Useful in debugging but drastically increases the
    # log size.
    # Default: no
    #LogClean yes
    # Use system logger (can work together with LogFile).
    # Default: no
    #LogSyslog yes
    # Specify the type of syslog messages - please refer to 'man syslog'
    # for facility names.
    # Default: LOG_LOCAL6
    #LogFacility LOG_MAIL
    # Enable verbose logging.
    # Default: no
    #LogVerbose yes
    # Log additional information about the infected file, such as its
    # size and hash, together with the virus name.
    #ExtendedDetectionInfo yes
    # This option allows you to save a process identifier of the listening
    # daemon (main thread).
    # Default: disabled
    PidFile /run/clamav/clamd.pid
    # Optional path to the global temporary directory.
    # Default: system specific (usually /tmp or /var/tmp).
    TemporaryDirectory /tmp
    # Path to the database directory.
    # Default: hardcoded (depends on installation options)
    DatabaseDirectory /var/lib/clamav
    # Only load the official signatures published by the ClamAV project.
    # Default: no
    OfficialDatabaseOnly yes
    # The daemon can work in local mode, network mode or both.
    # Due to security reasons we recommend the local mode.
    # Path to a local socket file the daemon will listen on.
    # Default: disabled (must be specified by a user)
    LocalSocket /var/lib/clamav/clamd.sock
    # Sets the group ownership on the unix socket.
    # Default: disabled (the primary group of the user running clamd)
    LocalSocketGroup clamav
    # Sets the permissions on the unix socket to the specified mode.
    # Default: disabled (socket is world accessible)
    #LocalSocketMode 660
    # Remove stale socket after unclean shutdown.
    # Default: yes
    #FixStaleSocket yes
    # TCP port address.
    # Default: no
    #TCPSocket 3310
    # TCP address.
    # By default we bind to INADDR_ANY, probably not wise.
    # Enable the following to provide some degree of protection
    # from the outside world.
    # Default: no
    #TCPAddr 127.0.0.1
    # Maximum length the queue of pending connections may grow to.
    # Default: 200
    #MaxConnectionQueueLength 30
    # Clamd uses FTP-like protocol to receive data from remote clients.
    # If you are using clamav-milter to balance load between remote clamd daemons
    # on firewall servers you may need to tune the options below.
    # Close the connection when the data size limit is exceeded.
    # The value should match your MTA's limit for a maximum attachment size.
    # Default: 25M
    #StreamMaxLength 10M
    # Limit port range.
    # Default: 1024
    #StreamMinPort 30000
    # Default: 2048
    #StreamMaxPort 32000
    # Maximum number of threads running at the same time.
    # Default: 10
    #MaxThreads 20
    # Waiting for data from a client socket will timeout after this time (seconds).
    # Default: 120
    #ReadTimeout 300
    # This option specifies the time (in seconds) after which clamd should
    # timeout if a client doesn't provide any initial command after connecting.
    # Default: 5
    #CommandReadTimeout 5
    # This option specifies how long to wait (in miliseconds) if the send buffer is full.
    # Keep this value low to prevent clamd hanging
    # Default: 500
    #SendBufTimeout 200
    # Maximum number of queued items (including those being processed by MaxThreads threads)
    # It is recommended to have this value at least twice MaxThreads if possible.
    # WARNING: you shouldn't increase this too much to avoid running out of file descriptors,
    # the following condition should hold:
    # MaxThreads*MaxRecursion + (MaxQueue - MaxThreads) + 6< RLIMIT_NOFILE (usual max is 1024)
    # Default: 100
    #MaxQueue 200
    # Waiting for a new job will timeout after this time (seconds).
    # Default: 30
    #IdleTimeout 60
    # Don't scan files and directories matching regex
    # This directive can be used multiple times
    # Default: scan all
    #ExcludePath ^/proc/
    #ExcludePath ^/sys/
    # Maximum depth directories are scanned at.
    # Default: 15
    #MaxDirectoryRecursion 20
    # Follow directory symlinks.
    # Default: no
    #FollowDirectorySymlinks yes
    # Follow regular file symlinks.
    # Default: no
    #FollowFileSymlinks yes
    # Scan files and directories on other filesystems.
    # Default: yes
    #CrossFilesystems yes
    # Perform a database check.
    # Default: 600 (10 min)
    #SelfCheck 600
    # Execute a command when virus is found. In the command string %v will
    # be replaced with the virus name.
    # Default: no
    #VirusEvent /usr/local/bin/send_sms 123456789 "VIRUS ALERT: %v"
    # Run as another user (clamd must be started by root for this option to work)
    # Default: don't drop privileges
    User clamav
    # Initialize supplementary group access (clamd must be started by root).
    # Default: no
    #AllowSupplementaryGroups no
    # Stop daemon when libclamav reports out of memory condition.
    #ExitOnOOM yes
    # Don't fork into background.
    # Default: no
    #Foreground yes
    # Enable debug messages in libclamav.
    # Default: no
    #Debug yes
    # Do not remove temporary files (for debug purposes).
    # Default: no
    #LeaveTemporaryFiles yes
    # Detect Possibly Unwanted Applications.
    # Default: no
    #DetectPUA yes
    # Exclude a specific PUA category. This directive can be used multiple times.
    # See http://www.clamav.net/support/pua for the complete list of PUA
    # categories.
    # Default: Load all categories (if DetectPUA is activated)
    #ExcludePUA NetTool
    #ExcludePUA PWTool
    # Only include a specific PUA category. This directive can be used multiple
    # times.
    # Default: Load all categories (if DetectPUA is activated)
    #IncludePUA Spy
    #IncludePUA Scanner
    #IncludePUA RAT
    # In some cases (eg. complex malware, exploits in graphic files, and others),
    # ClamAV uses special algorithms to provide accurate detection. This option
    # controls the algorithmic detection.
    # Default: yes
    #AlgorithmicDetection yes
    ## Executable files
    # PE stands for Portable Executable - it's an executable file format used
    # in all 32 and 64-bit versions of Windows operating systems. This option allows
    # ClamAV to perform a deeper analysis of executable files and it's also
    # required for decompression of popular executable packers such as UPX, FSG,
    # and Petite. If you turn off this option, the original files will still be
    # scanned, but without additional processing.
    # Default: yes
    #ScanPE yes
    # Executable and Linking Format is a standard format for UN*X executables.
    # This option allows you to control the scanning of ELF files.
    # If you turn off this option, the original files will still be scanned, but
    # without additional processing.
    # Default: yes
    #ScanELF yes
    # With this option clamav will try to detect broken executables (both PE and
    # ELF) and mark them as Broken.Executable.
    # Default: no
    #DetectBrokenExecutables yes
    ## Documents
    # This option enables scanning of OLE2 files, such as Microsoft Office
    # documents and .msi files.
    # If you turn off this option, the original files will still be scanned, but
    # without additional processing.
    # Default: yes
    #ScanOLE2 yes
    # With this option enabled OLE2 files with VBA macros, which were not
    # detected by signatures will be marked as "Heuristics.OLE2.ContainsMacros".
    # Default: no
    #OLE2BlockMacros no
    # This option enables scanning within PDF files.
    # If you turn off this option, the original files will still be scanned, but
    # without decoding and additional processing.
    # Default: yes
    #ScanPDF yes
    ## Mail files
    # Enable internal e-mail scanner.
    # If you turn off this option, the original files will still be scanned, but
    # without parsing individual messages/attachments.
    # Default: yes
    #ScanMail yes
    # Scan RFC1341 messages split over many emails.
    # You will need to periodically clean up $TemporaryDirectory/clamav-partial directory.
    # WARNING: This option may open your system to a DoS attack.
    # Never use it on loaded servers.
    # Default: no
    #ScanPartialMessages yes
    # With this option enabled ClamAV will try to detect phishing attempts by using
    # signatures.
    # Default: yes
    #PhishingSignatures yes
    # Scan URLs found in mails for phishing attempts using heuristics.
    # Default: yes
    #PhishingScanURLs yes
    # Always block SSL mismatches in URLs, even if the URL isn't in the database.
    # This can lead to false positives.
    # Default: no
    #PhishingAlwaysBlockSSLMismatch no
    # Always block cloaked URLs, even if URL isn't in database.
    # This can lead to false positives.
    # Default: no
    #PhishingAlwaysBlockCloak no
    # Allow heuristic match to take precedence.
    # When enabled, if a heuristic scan (such as phishingScan) detects
    # a possible virus/phish it will stop scan immediately. Recommended, saves CPU
    # scan-time.
    # When disabled, virus/phish detected by heuristic scans will be reported only at
    # the end of a scan. If an archive contains both a heuristically detected
    # virus/phish, and a real malware, the real malware will be reported
    # Keep this disabled if you intend to handle "*.Heuristics.*" viruses
    # differently from "real" malware.
    # If a non-heuristically-detected virus (signature-based) is found first,
    # the scan is interrupted immediately, regardless of this config option.
    # Default: no
    #HeuristicScanPrecedence yes
    ## Data Loss Prevention (DLP)
    # Enable the DLP module
    # Default: No
    #StructuredDataDetection yes
    # This option sets the lowest number of Credit Card numbers found in a file
    # to generate a detect.
    # Default: 3
    #StructuredMinCreditCardCount 5
    # This option sets the lowest number of Social Security Numbers found
    # in a file to generate a detect.
    # Default: 3
    #StructuredMinSSNCount 5
    # With this option enabled the DLP module will search for valid
    # SSNs formatted as xxx-yy-zzzz
    # Default: yes
    #StructuredSSNFormatNormal yes
    # With this option enabled the DLP module will search for valid
    # SSNs formatted as xxxyyzzzz
    # Default: no
    #StructuredSSNFormatStripped yes
    ## HTML
    # Perform HTML normalisation and decryption of MS Script Encoder code.
    # Default: yes
    # If you turn off this option, the original files will still be scanned, but
    # without additional processing.
    #ScanHTML yes
    ## Archives
    # ClamAV can scan within archives and compressed files.
    # If you turn off this option, the original files will still be scanned, but
    # without unpacking and additional processing.
    # Default: yes
    #ScanArchive yes
    # Mark encrypted archives as viruses (Encrypted.Zip, Encrypted.RAR).
    # Default: no
    #ArchiveBlockEncrypted no
    ## Limits
    # The options below protect your system against Denial of Service attacks
    # using archive bombs.
    # This option sets the maximum amount of data to be scanned for each input file.
    # Archives and other containers are recursively extracted and scanned up to this
    # value.
    # Value of 0 disables the limit
    # Note: disabling this limit or setting it too high may result in severe damage
    # to the system.
    # Default: 100M
    #MaxScanSize 150M
    # Files larger than this limit won't be scanned. Affects the input file itself
    # as well as files contained inside it (when the input file is an archive, a
    # document or some other kind of container).
    # Value of 0 disables the limit.
    # Note: disabling this limit or setting it too high may result in severe damage
    # to the system.
    # Default: 25M
    #MaxFileSize 30M
    # Nested archives are scanned recursively, e.g. if a Zip archive contains a RAR
    # file, all files within it will also be scanned. This options specifies how
    # deeply the process should be continued.
    # Note: setting this limit too high may result in severe damage to the system.
    # Default: 16
    #MaxRecursion 10
    # Number of files to be scanned within an archive, a document, or any other
    # container file.
    # Value of 0 disables the limit.
    # Note: disabling this limit or setting it too high may result in severe damage
    # to the system.
    # Default: 10000
    #MaxFiles 15000
    ## Clamuko settings
    # Enable Clamuko. Dazuko must be configured and running. Clamuko supports
    # both Dazuko (/dev/dazuko) and DazukoFS (/dev/dazukofs.ctrl). DazukoFS
    # is the preferred option. For more information please visit www.dazuko.org
    # Default: no
    #ClamukoScanOnAccess yes
    # The number of scanner threads that will be started (DazukoFS only).
    # Having multiple scanner threads allows Clamuko to serve multiple
    # processes simultaneously. This is particularly beneficial on SMP machines.
    # Default: 3
    #ClamukoScannerCount 3
    # Don't scan files larger than ClamukoMaxFileSize
    # Value of 0 disables the limit.
    # Default: 5M
    #ClamukoMaxFileSize 10M
    # Set access mask for Clamuko (Dazuko only).
    # Default: no
    #ClamukoScanOnOpen yes
    #ClamukoScanOnClose yes
    #ClamukoScanOnExec yes
    # Set the include paths (all files inside them will be scanned). You can have
    # multiple ClamukoIncludePath directives but each directory must be added
    # in a seperate line. (Dazuko only)
    # Default: disabled
    #ClamukoIncludePath /home
    #ClamukoIncludePath /students
    # Set the exclude paths. All subdirectories are also excluded. (Dazuko only)
    # Default: disabled
    #ClamukoExcludePath /home/bofh
    # With this option you can whitelist specific UIDs. Processes with these UIDs
    # will be able to access all files.
    # This option can be used multiple times (one per line).
    # Default: disabled
    #ClamukoExcludeUID 0
    # With this option enabled ClamAV will load bytecode from the database.
    # It is highly recommended you keep this option on, otherwise you'll miss detections for many new viruses.
    # Default: yes
    #Bytecode yes
    # Set bytecode security level.
    # Possible values:
    # None - no security at all, meant for debugging. DO NOT USE THIS ON PRODUCTION SYSTEMS
    # This value is only available if clamav was built with --enable-debug!
    # TrustSigned - trust bytecode loaded from signed .c[lv]d files,
    # insert runtime safety checks for bytecode loaded from other sources
    # Paranoid - don't trust any bytecode, insert runtime checks for all
    # Recommended: TrustSigned, because bytecode in .cvd files already has these checks
    # Note that by default only signed bytecode is loaded, currently you can only
    # load unsigned bytecode in --enable-debug mode.
    # Default: TrustSigned
    #BytecodeSecurity TrustSigned
    # Set bytecode timeout in miliseconds.
    # Default: 5000
    # BytecodeTimeout 1000
    My freshclam.conf:
    ## Please read the freshclam.conf(5) manual before editing this file.
    # Comment or remove the line below.
    #Example
    # Path to the database directory.
    # WARNING: It must match clamd.conf's directive!
    # Default: hardcoded (depends on installation options)
    #DatabaseDirectory /var/lib/clamav
    # Path to the log file (make sure it has proper permissions)
    # Default: disabled
    UpdateLogFile /var/log/clamav/freshclam.log
    # Maximum size of the log file.
    # Value of 0 disables the limit.
    # You may use 'M' or 'm' for megabytes (1M = 1m = 1048576 bytes)
    # and 'K' or 'k' for kilobytes (1K = 1k = 1024 bytes).
    # in bytes just don't use modifiers.
    # Default: 1M
    #LogFileMaxSize 2M
    # Log time with each message.
    # Default: no
    #LogTime yes
    # Enable verbose logging.
    # Default: no
    #LogVerbose yes
    # Use system logger (can work together with UpdateLogFile).
    # Default: no
    #LogSyslog yes
    # Specify the type of syslog messages - please refer to 'man syslog'
    # for facility names.
    # Default: LOG_LOCAL6
    #LogFacility LOG_MAIL
    # This option allows you to save the process identifier of the daemon
    # Default: disabled
    #PidFile /var/run/freshclam.pid
    # By default when started freshclam drops privileges and switches to the
    # "clamav" user. This directive allows you to change the database owner.
    # Default: clamav (may depend on installation options)
    #DatabaseOwner clamav
    # Initialize supplementary group access (freshclam must be started by root).
    # Default: no
    #AllowSupplementaryGroups yes
    # Use DNS to verify virus database version. Freshclam uses DNS TXT records
    # to verify database and software versions. With this directive you can change
    # the database verification domain.
    # WARNING: Do not touch it unless you're configuring freshclam to use your
    # own database verification domain.
    # Default: current.cvd.clamav.net
    #DNSDatabaseInfo current.cvd.clamav.net
    # Uncomment the following line and replace XY with your country
    # code. See http://www.iana.org/cctld/cctld-whois.htm for the full list.
    # You can use db.XY.ipv6.clamav.net for IPv6 connections.
    #DatabaseMirror db.XY.clamav.net
    # database.clamav.net is a round-robin record which points to our most
    # reliable mirrors. It's used as a fall back in case db.XY.clamav.net is
    # not working. DO NOT TOUCH the following line unless you know what you
    # are doing.
    DatabaseMirror database.clamav.net
    # How many attempts to make before giving up.
    # Default: 3 (per mirror)
    #MaxAttempts 5
    # With this option you can control scripted updates. It's highly recommended
    # to keep it enabled.
    # Default: yes
    #ScriptedUpdates yes
    # By default freshclam will keep the local databases (.cld) uncompressed to
    # make their handling faster. With this option you can enable the compression;
    # the change will take effect with the next database update.
    # Default: no
    #CompressLocalDatabase no
    # With this option you can provide custom sources (http:// or file://) for
    # database files. This option can be used multiple times.
    # Default: no custom URLs
    #DatabaseCustomURL http://myserver.com/mysigs.ndb
    #DatabaseCustomURL file:///mnt/nfs/local.hdb
    # Number of database checks per day.
    # Default: 12 (every two hours)
    #Checks 24
    # Proxy settings
    # Default: disabled
    #HTTPProxyServer myproxy.com
    #HTTPProxyPort 1234
    #HTTPProxyUsername myusername
    #HTTPProxyPassword mypass
    # If your servers are behind a firewall/proxy which applies User-Agent
    # filtering you can use this option to force the use of a different
    # User-Agent header.
    # Default: clamav/version_number
    #HTTPUserAgent SomeUserAgentIdString
    # Use aaa.bbb.ccc.ddd as client address for downloading databases. Useful for
    # multi-homed systems.
    # Default: Use OS'es default outgoing IP address.
    #LocalIPAddress aaa.bbb.ccc.ddd
    # Send the RELOAD command to clamd.
    # Default: no
    NotifyClamd /etc/clamav/clamd.conf
    # Run command after successful database update.
    # Default: disabled
    #OnUpdateExecute command
    # Run command when database update process fails.
    # Default: disabled
    #OnErrorExecute command
    # Run command when freshclam reports outdated version.
    # In the command string %v will be replaced by the new version number.
    # Default: disabled
    #OnOutdatedExecute command
    # Don't fork into background.
    # Default: no
    #Foreground yes
    # Enable debug messages in libclamav.
    # Default: no
    #Debug yes
    # Timeout in seconds when connecting to database server.
    # Default: 30
    #ConnectTimeout 60
    # Timeout in seconds when reading from database server.
    # Default: 30
    #ReceiveTimeout 60
    # With this option enabled, freshclam will attempt to load new
    # databases into memory to make sure they are properly handled
    # by libclamav before replacing the old ones.
    # Default: yes
    #TestDatabases yes
    # When enabled freshclam will submit statistics to the ClamAV Project about
    # the latest virus detections in your environment. The ClamAV maintainers
    # will then use this data to determine what types of malware are the most
    # detected in the field and in what geographic area they are.
    # Freshclam will connect to clamd in order to get recent statistics.
    # Default: no
    #SubmitDetectionStats /path/to/clamd.conf
    # Country of origin of malware/detection statistics (for statistical
    # purposes only). The statistics collector at ClamAV.net will look up
    # your IP address to determine the geographical origin of the malware
    # reported by your installation. If this installation is mainly used to
    # scan data which comes from a different location, please enable this
    # option and enter a two-letter code (see http://www.iana.org/domains/root/db/)
    # of the country of origin.
    # Default: disabled
    #DetectionStatsCountry country-code
    # This option enables support for our "Personal Statistics" service.
    # When this option is enabled, the information on malware detected by
    # your clamd installation is made available to you through our website.
    # To get your HostID, log on http://www.stats.clamav.net and add a new
    # host to your host list. Once you have the HostID, uncomment this option
    # and paste the HostID here. As soon as your freshclam starts submitting
    # information to our stats collecting service, you will be able to view
    # the statistics of this clamd installation by logging into
    # http://www.stats.clamav.net with the same credentials you used to
    # generate the HostID. For more information refer to:
    # http://www.clamav.net/support/faq/faq-cctts/
    # This feature requires SubmitDetectionStats to be enabled.
    # Default: disabled
    #DetectionStatsHostID unique-id
    # This option enables support for Google Safe Browsing. When activated for
    # the first time, freshclam will download a new database file (safebrowsing.cvd)
    # which will be automatically loaded by clamd and clamscan during the next
    # reload, provided that the heuristic phishing detection is turned on. This
    # database includes information about websites that may be phishing sites or
    # possible sources of malware. When using this option, it's mandatory to run
    # freshclam at least every 30 minutes.
    # Freshclam uses the ClamAV's mirror infrastructure to distribute the
    # database and its updates but all the contents are provided under Google's
    # terms of use. See http://code.google.com/support/bin/answer.py?answer=70015
    # and http://safebrowsing.clamav.net for more information.
    # Default: disabled
    #SafeBrowsing yes
    # This option enables downloading of bytecode.cvd, which includes additional
    # detection mechanisms and improvements to the ClamAV engine.
    # Default: enabled
    #Bytecode yes
    # Download an additional 3rd party signature database distributed through
    # the ClamAV mirrors. Here you can find a list of available databases:
    # http://www.clamav.net/download/cvd/3rdparty
    # This option can be used multiple times.
    #ExtraDatabase dbname1
    #ExtraDatabase dbname2
    Any help is much appreciated.

    MatejLach wrote:
    clamd is running, user and group clamav all have the relevant permissions as far as I can tell, however upon scanning my mail, I always end up with the following error:
    Scanning error:
    /home/username/.claws-mail/mimetmp/0000000e.mimetmp: lstat() failed: Permission denied. ERROR
    Seems like a permissions error to me... maybe check the actual file it is attempting to scan... I know it is in your home folder, but just to be sure, you might want to check that everything is sane.

  • How to change the replication group information after db files are created

    Since group information is persisted in the database, I am wondering if there is a way to update the information.
    We want to implement some kind of Berkeley DB master relay mechanism for our two data centers, which has slow link in between. Basically have one master populating a database file and launch another two node as master to replay that to other nodes of its own group. It will be much efficient this way so we don't have to copy the data multiple times over the slow link.
    We periodically (once a day) update the Berkeley DB content from customer's feed on a backend node and upload (rsync) the Berkeley DB File to two the data centers. We would like to have a master node in each data center to read the pre-populated data file, replicate the changes to the web node (read only) while they are still running. I simulated local and if I trick the nodeName and nodeHostPort setting, it should work (basically, fake the replication node on the backend node using tampered hostfile so they get registerred). However, it is not very convenient and definitely a dangerous hack on the production servers.
    If there is a way, after the creation, to update the group information (for example, change all the nodes information) without corrupt the log file/replication stream, it will be much easier for us. Basically, we would like to have the node/group information and data file de-coupled?
    Any ideas how to do that, or is there a better way to design such a replay of data using Berkeley DB?
    Thanks in advance!

    2. You mentioned to not clean up the log file. Is there a point where I can safely call clean up on the environment when BDB is still online as I can imagine we will run out of space very soon if we don't clean up.The approach outlined above (steps 1 to 5) will ensure that no log files are deleted on A while you are updating B and C. The use of DbBackup ensures this. For more information on how this works, see the DbBackup javadoc.
    Whether this causes you to run out of disk space on A is something you'll have to evaluate for yourself. It depends on the write rate on A and how long it takes to do the copy to B and C. If this is a problem, you could make a quick local copy of the environment on A, and then transfer that copy to B/C. But you must prohibit log file deletion during the copy, using DbBackup, or the copy will be invalid.
    You should perform explicit JE log cleaning (including a checkpoint) before doing the copy to B/C. This will reduce the number of files that are copied to B/C, and will reduce the likelihood that you'll fill the disk on A. See the javadoc for Environment.cleanLog for details on how to do an explicit log cleaning.
    In your earlier post, it sounded like the updates to A were in batch mode -- done all at once at a specific time of day. If so, you can do the copy to B/C after the update to A. In that case, I don't understand why you are afraid of filling the disk on A, since updates would not be occurring during the copy to B/C.
    --mark                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • SCCM's OSD (not MDT): Task sequence can be tweaked into imaging Windows+VHD Native Boot, but can it go all the way and deploy?

    Hello All,
    What I am trying to do is use SCCM's own OSD Task Sequence / Windows PE to deploy an operating system that boots using VHD Native Boot. (C:\ = VHD File  with Windows, D:\ Data drive with BCDBoot).
    MDT 2013 Can do it I've been told, but I am putting off MDT until Windows 10 if I can get away with it.
    TechNet VHD Native Boot on Windows 8.1:
    http://technet.microsoft.com/en-us/library/hh825689.aspx
    http://technet.microsoft.com/en-us/library/hh825691.aspx
    The good news is it is working up to the "Apply Operating System" phase, but that apply operating system phase is reported as an error even though it completes successfully. It can't clean up the SMSTS folder it's looking for on the C:\ because
    it's been moved over to the D:\ by a diskpart script. We are left with the deployment working but requiring IT staff to deal with the OOBE Personalization wizard and adding each PC to the domain manually. From that point on the SCCM client can do the rest,
    which works for US before we upgrade to Windows 10 with utilizing MDT.
    I am not talking about deploying an OS to a VHD file and putting that file on a network share i.e.
    http://blogs.technet.com/b/configurationmgr/archive/2013/10/31/new-in-system-center-2012-r2-configuration-manager-deploying-an-operating-system-to-a-virtual-hard-drive-vhd.aspx
    I reported getting the diskpart script working first here:
    https://social.technet.microsoft.com/Forums/en-US/ff124f09-1d2e-4fc4-a5b6-63b683f3d208/native-vhd-boot-deployments-from-sccm-2012-r2?forum=configmanagerosd
    Here it is:
    rem work around any USB disk left in or any CDROM detected by PE as drive D
    select volume D
    assign letter=F noerr
    rem select the formatted volume and reassign it's drive letter
    select volume C
    assign letter=D
    rem create and setup VHD file
    create vdisk file=D:\DEV_WIN81.VHD maximum=250000 type=expandable
    select vdisk file=D:\DEV_WIN81.VHD
    attach vdisk
    create partition primary
    active
    format FS=NTFS quick label="Developer Win81 VHD"
    assign letter=C
    rescan
    exit
    (type=fixed is better for performance - we'll surely activate when we have dual boot 8.1 / Windows 10 later for the Win10 VHD's)
    The Task Sequence looks like this:
    I'd like to add a few more steps after apply operating system if I can, but I have to resolve this error with "Apply Operating system before I can go further."
    Question:
    Can an OSD guru tell me if there are any Task Sequence Variables we could throw at this to make the Apply Operating System sequence complete without error so we can do all SCCM OSD Deployment steps?
    If we can, then someone (not me) gets to add a new TechNet blog post about this being possible. It's my understanding presently that only MDT can support deploying WIM files into VHDs on Workstations, that boot them.
    The install image was created using dism to convert a VHD from a Hyper-V host into a wim. I know I'm meant to use SCCM to capture it, but I don't think that's causing this problem because when we are deploying from that image to a HDD without VHD we don't
    get any issues.
    I'm only allowed enough characters to paste the tail end of the apply operating system phase only:
    <![LOG[Execution engine result code: Success (0)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:929">
    <![LOG[Cleaning Up.]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:675">
    <![LOG[Removing Authenticator]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:686">
    <![LOG[shKey.DeleteValue( c_szRegValue_SecurityToken ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\ccmutillib\ccmutillib.cpp,1660)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmutillib.cpp:1660">
    <![LOG[Cleaning up task sequence folder]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2329">
    <![LOG[Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="ccmfile.cpp:1056">
    <![LOG[hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmfile.cpp:1218">
    <![LOG[Failed to delete directory 'C:\_SMSTaskSequence']LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="ccmfile.cpp:1218">
    <![LOG[(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION, pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6675)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6675">
    <![LOG[SetNamedSecurityInfo() failed.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6675">
    <![LOG[SetObjectOwner() failed. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6687">
    <![LOG[SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6772)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6772">
    <![LOG[RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6816">
    <![LOG[RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:6900">
    <![LOG[Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
    <![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
    <![LOG[Deleting volume ID file D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
    <![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
    <![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="environmentlib.cpp:910">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:228">
    <![LOG[Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:731">
    <![LOG[Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:827">
    <![LOG[==========[ TsProgressUI started in process 8012 ]==========]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:330">
    <![LOG[Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="0" thread="8040" file="winmain.cpp:332">
    <![LOG[Unregistering COM classes]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:204">
    <![LOG[Unregistering class objects]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:495">
    <![LOG[Shutdown complete.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:512">
    <![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:1123">
    <![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2903">
    <![LOG[Sending success status message]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:784">
    <![LOG[MP server http://OUR-SCCM.ourcompany.com. Ports 80,443. CRL=false.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5881">
    <![LOG[Setting authenticator]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5903">
    <![LOG[Set authenticator in transport]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:7734">
    <![LOG[Sending StatusMessage]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:4023">
    <![LOG[Setting message signatures.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1295">
    <![LOG[Setting the authenticator.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1325">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: OUR-SCCM.ourcompany.com:80 CCM_POST /ccm_system/request]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:8604">
    <![LOG[Request was successful.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:8939">
    <![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:811">
    <![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:811">
    <![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:842">
    <![LOG[End program: ]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:805">
    <![LOG[Finalize logging request ignored from process 856]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tslogging.cpp:1737">
    <![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="commandline.cpp:1123">
    <![LOG[Task Sequence Manager returned code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmediawizardcontrol.cpp:2180">
    <![LOG[Exiting with return code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmbootstrap.cpp:1238">
    <![LOG[Execution complete.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:693">
    <![LOG[hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentscope.cpp:493">
    <![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:335">
    <![LOG[this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:553">
    <![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="utils.cpp:811">
    <![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:811">
    <![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:842">
    <![LOG[End program: ]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:725">
    <![LOG[Finalizing logging from process 752]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1741">
    <![LOG[Finalizing logs to root of first available drive]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1583">
    <![LOG[Successfully finalized logs to D:\SMSTSLog]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1640">
    <![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="tslogging.cpp:584">
    MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

    I have already set it to FALSE. The solution to this will be some different OSD Task Sequence variables or a statement that it can't be made to work.
    I believe that setting defines what volume will be the BOOT / OS Drive Letter. Some people were getting D:\WINDOWS as their boot volume drive letter. Setting to true means whatever was the System Drive letter (usually C) in the image will remain as such
    after it was was applied, setting it to false will make the system have the same drive letter arrangement as what Windows PE detects. In my case I set it to false so that no matter what the new VHD file setup as drive C will be the system drive. I'll set it
    to true on the next deployment but I expect there to be no difference, because in both PE and the WIM the installation volume is the C:.
    We are talking about the DRIVE LETTERS Windows PE SCCM OSD is using for it's temporary files - and how we can manipulate these locations using OSD Task Sequence Variables, so the Apply OS doesn't try and clean up files that are not there
    - and fail with an error if you have added a VHD Native Boot volume.
    This OSDPreserveDriveLetter setting isn't having any effect on the problem here.
    I believe that Format step is setting some task variables used by the OSD Deployment process - telling it where to store it's temporary files. However between the Format Disks and Apply operating system steps the OSD Task Sequence isn't picking up on the
    fact what was the C:\ after Format HDD step is now the D:\ .
    A developer who has an understanding of how the OSD boot process executes in order would be able to see what's going on here.
    MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

  • 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..

  • Multiple errors attempting to capture a Windows 8 reference image after booting from USB (Dell Latitude 10)

    From results.xml:
    <?xml version="1.0"?>
    <Results><Errors>8</Errors><Warnings>0</Warnings><RetVal>-2147467259</RetVal><DeploymentType>CUSTOM</DeploymentType><Messages><![CDATA[FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive. See BDD.LOG for more information.
    Litetouch deployment failed, Return Code = -2147467259 0x80004005
    Failed to run the action: Apply Windows PE.
    Unknown error (Error: 00001550; Source: Unknown)
    The execution of the group (Capture Image) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)
    Failed to run the last action: Apply Windows PE. Execution of task sequence failed.
    Unknown error (Error: 00001550; Source: Unknown)
    Task Sequence Engine failed! Code: enExecutionFail
    Task sequence execution failed with error code 80004005
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]]></Messages></Results>
    I have not only regenerated my boot files while updating my deployment share, I have completely rebuilt the MDT 2012 deployment share from scratch, and I'm still getting the exact same errors. I can't figure out what is causing this. The only hits for these
    errors seemed to say that the -214... error is likely related to a missing file, but I don't know how to figure out what that might be. I don't know what the FAILURE ( 5456 ) could be caused by, either, although it seems to be related to not knowing what partition
    should be imaged or imaged to. I haven't been able to find any reference to MDT needing a partition to image from/to set in a CS.ini property or in a task variable.
    I am running a modified version of the Sysprep and Capture Task Sequence (set up as described at http://bjtechnews.org/2012/06/01/mdt-2012-capturing-a-reference-image-part-ii/, it's basically the default settings for that TS with the sysprep step disabled and
    the "Set Image Folder" task variable created per that post--I ran sysprep myself, manually, on the machine before shutting it down to boot from USB) after booting a Dell Latitude 10 tablet from a USB drive created by extracting the contents of the
    MDT 2012 DeploymentShare$\Boot\LiteTouchpe_x86.iso to a FAT32-formatted volume.

    Here is the second part of BDD.log:
    <![LOG[VSSMaxSize not specified using 5% of volume.]LOG]!><time="21:18:42.000+000" date="07-23-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Logs contained 8 errors and 0 warnings.]LOG]!><time="21:18:42.000+000" date="07-23-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[No Windows PE image to delete.]LOG]!><time="21:18:42.000+000" date="07-23-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Stripping BDD commands from unattend.xml template.]LOG]!><time="21:18:42.000+000" date="07-23-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Modified unattend.xml saved to C:\windows\panther\unattend.xml]LOG]!><time="21:18:42.000+000" date="07-23-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Checking mapped network drive.]LOG]!><time="21:18:43.000+000" date="07-23-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[testing drive Z: mapped to \\NCSD-WDS\DeploymentShare$]LOG]!><time="21:18:43.000+000" date="07-23-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Disconnecting drive Z: mapped to \\NCSD-WDS\DeploymentShare$]LOG]!><time="21:18:43.000+000" date="07-23-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[testing drive Y: mapped to \\ncsd-wds.ncsd.local\deploymentshare$]LOG]!><time="21:18:43.000+000" date="07-23-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Cleaning up C:\MININT directory.]LOG]!><time="21:18:43.000+000" date="07-23-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Cleaning up TOOLS, SCRIPTS, and PACKAGES directories.]LOG]!><time="21:18:43.000+000" date="07-23-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Removing C:\MININT folder (final log entry)]LOG]!><time="21:18:44.000+000" date="07-23-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Not Wizard = False]LOG]!><time="00:44:05.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property WizardComplete is now = N]LOG]!><time="00:44:07.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[ Open Control File: TaskSequences]LOG]!><time="00:44:08.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[CleanStartItems Complete]LOG]!><time="00:53:55.000+000" date="07-24-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Removing C:\MININT folder (final log entry)]LOG]!><time="00:53:55.000+000" date="07-24-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="00:53:55.000+000" date="07-24-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\MININT-IDKMK2C\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="00:53:55.000+000" date="07-24-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\MININT-IDKMK2C\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="00:53:55.000+000" date="07-24-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDiskPartition : \\MININT-IDKMK2C\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #2" \\MININT-IDKMK2C\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="00:53:55.000+000" date="07-24-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\MININT-IDKMK2C\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="00:53:56.000+000" date="07-24-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDiskPartition : \\MININT-IDKMK2C\root\cimv2:Win32_DiskPartition.DeviceID="Disk #1, Partition #0" \\MININT-IDKMK2C\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="00:53:56.000+000" date="07-24-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\MININT-IDKMK2C\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE1"]LOG]!><time="00:53:56.000+000" date="07-24-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ZTIUtility!GetAllFixedDrives = C:]LOG]!><time="00:53:56.000+000" date="07-24-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Not Wizard = False]LOG]!><time="00:54:54.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property WizardComplete is now = N]LOG]!><time="00:54:55.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[ Open Control File: TaskSequences]LOG]!><time="00:54:56.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property TaskSequenceID is now = CAPTURE001]LOG]!><time="00:55:00.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Found Task Sequence Item: //step[@type='BDD_InstallOS']]LOG]!><time="00:55:01.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Found Task Sequence step of type //step[@type='BDD_InstallOS'] = False]LOG]!><time="00:55:01.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Task Sequence does not contain an OS and does not contain a LTIApply.wsf step, possibly a Custom Step or a Client Replace.]LOG]!><time="00:55:01.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[DeploymentType = CUSTOM]LOG]!><time="00:55:01.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property ImageProcessor is now = ]LOG]!><time="00:55:02.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property OSGUID is now = ]LOG]!><time="00:55:02.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property TaskSequenceName is now = Capture reference image]LOG]!><time="00:55:02.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property TaskSequenceVersion is now = 1.0]LOG]!><time="00:55:02.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property TaskSequenceTemplate is now = CaptureOnly.xml]LOG]!><time="00:55:02.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property OSGUID is now = {9c976969-ab45-405b-82e7-d8a429228a67}]LOG]!><time="00:55:03.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property ImageIndex is now = 1]LOG]!><time="00:55:03.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property ImageSize is now = 7934]LOG]!><time="00:55:03.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property ImageFlags is now = Professional]LOG]!><time="00:55:03.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property ImageBuild is now = 6.2.9200.16384]LOG]!><time="00:55:03.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property ImageProcessor is now = x86]LOG]!><time="00:55:04.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property ImageLanguage001 is now = en-US]LOG]!><time="00:55:04.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[InstallFromPath: \\NCSD-WDS\Latitude10Deploy$\Operating Systems\Windows 8 Pro x86\Sources\install.wim]LOG]!><time="00:55:04.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property InstallFromPath is now = \\ncsd-wds\latitude10deploy$\Operating Systems\Windows 8 Pro x86\sources\install.wim]LOG]!><time="00:55:04.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[SourcePath: \\NCSD-WDS\Latitude10Deploy$\Operating Systems\Windows 8 Pro x86]LOG]!><time="00:55:04.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property SourcePath is now = \\NCSD-WDS\Latitude10Deploy$\Operating Systems\Windows 8 Pro x86]LOG]!><time="00:55:05.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Found Task Sequence Item: //step[@type='BDD_InstallRoles']]LOG]!><time="00:55:05.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Found Task Sequence step of type //step[@type='BDD_InstallRoles'] = ]LOG]!><time="00:55:05.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Found Task Sequence Item: //step[@type='BDD_InstallApplication' and ./defaultVarList/variable[@name='ApplicationGUID'] and ./defaultVarList[variable='']]]LOG]!><time="00:55:05.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Found Task Sequence step of type //step[@type='BDD_InstallApplication' and ./defaultVarList/variable[@name='ApplicationGUID'] and ./defaultVarList[variable='']] = ]LOG]!><time="00:55:06.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Found Task Sequence Item: //step[@name='Create WIM']]LOG]!><time="00:55:06.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Found Task Sequence step of type //step[@name='Create WIM'] = True]LOG]!><time="00:55:06.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Found Task Sequence Item: //step[@name='Create WIM']]LOG]!><time="00:55:19.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Found Task Sequence step of type //step[@name='Create WIM'] = True]LOG]!><time="00:55:19.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Validating connection to \\NCSD-WDS\Latitude10Deploy$\Captures]LOG]!><time="00:55:32.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Already connected to server NCSD-WDS as that is where this script is running from.]LOG]!><time="00:55:33.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property TSGuid is now = {ed8ed1ac-ab1a-448d-97b5-0d4cb1f7ef95}]LOG]!><time="00:55:38.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property OSGUID is now = ]LOG]!><time="00:55:39.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property DeploymentType is now = CUSTOM]LOG]!><time="00:55:39.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[<Message containing password has been suppressed>]LOG]!><time="00:55:39.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property DoCapture is now = YES]LOG]!><time="00:55:39.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property ComputerBackupLocation is now = \\NCSD-WDS\Latitude10Deploy$\Captures]LOG]!><time="00:55:39.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property BackupFile is now = CAPTURE001.wim]LOG]!><time="00:55:40.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property WizardComplete is now = Y]LOG]!><time="00:55:40.000+000" date="07-24-2013" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Setting variable ComputerBackupLocation to value \\ncsd-wds.ncsd.local\Latitude10Deploy$\Captures]LOG]!><time="00:55:45.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[Property ComputerBackupLocation is now = \\ncsd-wds.ncsd.local\Latitude10Deploy$\Captures]LOG]!><time="00:55:45.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[ZTISetVariable processing completed successfully.]LOG]!><time="00:55:45.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[Event 41001 sent: ZTISetVariable processing completed successfully.]LOG]!><time="00:55:46.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[Setting variable ImageBuild to value 6.2.9200]LOG]!><time="00:55:47.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[Property ImageBuild is now = 6.2.9200]LOG]!><time="00:55:47.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[ZTISetVariable processing completed successfully.]LOG]!><time="00:55:47.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[Event 41001 sent: ZTISetVariable processing completed successfully.]LOG]!><time="00:55:48.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[Setting variable ImageFlags to value %OSSKU%]LOG]!><time="00:55:49.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[Property ImageFlags is now = %OSSKU%]LOG]!><time="00:55:49.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[ZTISetVariable processing completed successfully.]LOG]!><time="00:55:49.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[Event 41001 sent: ZTISetVariable processing completed successfully.]LOG]!><time="00:55:50.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[Setting variable PHASE to value STATERESTORE]LOG]!><time="00:55:51.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[Property PHASE is now = STATERESTORE]LOG]!><time="00:55:51.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[ZTISetVariable processing completed successfully.]LOG]!><time="00:55:51.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[Event 41001 sent: ZTISetVariable processing completed successfully.]LOG]!><time="00:55:52.000+000" date="07-24-2013" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[---------------- Initialization ----------------]LOG]!><time="00:55:53.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Validating connection to \\NCSD-WDS\Latitude10Deploy$]LOG]!><time="00:55:53.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Already connected to server NCSD-WDS as that is where this script is running from.]LOG]!><time="00:55:53.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[DestinationOSInstallType = BYDISKPARTITION]LOG]!><time="00:55:54.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Found: DestinationDisk: 0]LOG]!><time="00:55:54.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Found: DestinationPartition: 1]LOG]!><time="00:55:54.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No drive mapped to Disk Partition: \\MININT-IDKMK2C\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="00:55:54.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Unable to yield a target Partition (Special Recovery option for Litetouch).]LOG]!><time="00:55:54.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[DestinationDisk and Partition did not yield a target Partition.]LOG]!><time="00:55:54.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Destination Logical Drive was not specificed, defaulting to #:\]LOG]!><time="00:55:54.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Looking for Sysprep.inf in #:\sysprep\Sysprep.inf]LOG]!><time="00:55:55.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[The sysprep.inf file was not found.]LOG]!><time="00:55:55.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Property OSDAnswerFilePathSysprep is now = ]LOG]!><time="00:55:55.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[The unattend.txt file was not found.]LOG]!><time="00:55:55.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Found unattend.xml at \\NCSD-WDS\Latitude10Deploy$\Control\CAPTURE001\Unattend.xml, will copy to C:\MININT\Unattend.xml]LOG]!><time="00:55:55.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Copied \\NCSD-WDS\Latitude10Deploy$\Control\CAPTURE001\Unattend.xml to C:\MININT\Unattend.xml]LOG]!><time="00:55:55.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Property OSDAnswerFilePath is now = C:\MININT\Unattend.xml]LOG]!><time="00:55:55.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Loaded C:\MININT\Unattend.xml]LOG]!><time="00:55:55.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for ComputerName]LOG]!><time="00:55:56.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for FullName]LOG]!><time="00:55:56.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for OrgName]LOG]!><time="00:55:56.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for ProductKey]LOG]!><time="00:55:56.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for JoinDomain]LOG]!><time="00:55:56.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for MachineObjectOU]LOG]!><time="00:55:56.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for JoinWorkgroup]LOG]!><time="00:55:56.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for DomainAdmin]LOG]!><time="00:55:56.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[<Message containing password has been suppressed>]LOG]!><time="00:55:56.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for InputLocale]LOG]!><time="00:55:56.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for Language]LOG]!><time="00:55:57.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for LanguageGroup]LOG]!><time="00:55:57.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for SystemLocale]LOG]!><time="00:55:57.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for UserLocale]LOG]!><time="00:55:57.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for TimeZone]LOG]!><time="00:55:57.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for AutoLogon]LOG]!><time="00:55:57.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for AutoLogonCount]LOG]!><time="00:55:57.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for BitsPerPel]LOG]!><time="00:55:57.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for Xresolution]LOG]!><time="00:55:57.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for Yresolution]LOG]!><time="00:55:57.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for Vrefresh]LOG]!><time="00:55:58.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for AreaCode]LOG]!><time="00:55:58.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for CountryCode]LOG]!><time="00:55:58.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for Dialing]LOG]!><time="00:55:58.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for LongDistanceAccess]LOG]!><time="00:55:58.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for Home_Page]LOG]!><time="00:55:58.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for AutoMode]LOG]!><time="00:55:58.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for AutoUsers]LOG]!><time="00:55:59.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[//settings[@pass="windowsPE"]/component[@name="Microsoft-Windows-Setup"]/UpgradeData/Upgrade not found in C:\MININT\Unattend.xml, unable to update.]LOG]!><time="00:55:59.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for OSDComputerName]LOG]!><time="00:55:59.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for ProductKey]LOG]!><time="00:55:59.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Removed parent of //settings[@pass="windowsPE"]/component[@name="Microsoft-Windows-Setup"]/UserData/ProductKey/Key from C:\MININT\Unattend.xml because the value was blank.]LOG]!><time="00:55:59.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Removed //settings[@pass="specialize"]/component[@name="Microsoft-Windows-Shell-Setup"]/ProductKey from C:\MININT\Unattend.xml because the value was blank.]LOG]!><time="00:55:59.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for JoinDomain]LOG]!><time="00:55:59.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Removed //settings[@pass="specialize"]/component[@name="Microsoft-Windows-UnattendedJoin"]/Identification/MachineObjectOU from C:\MININT\Unattend.xml because the value was blank.]LOG]!><time="00:55:59.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for JoinWorkgroup]LOG]!><time="00:55:59.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for DomainAdmin]LOG]!><time="00:55:59.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for DomainAdminDomain]LOG]!><time="00:56:00.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[<Message containing password has been suppressed>]LOG]!><time="00:56:00.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Updated C:\MININT\Unattend.xml with InstallFromPath=\\ncsd-wds\latitude10deploy$\Operating Systems\Windows 8 Pro x86\sources\install.wim (value was .\Operating Systems\Windows 8 Pro x86\Sources\install.wim)]LOG]!><time="00:56:00.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[//settings[@pass="windowsPE"]/component[@name="Microsoft-Windows-Setup"]/ImageInstall/OSImage/InstallFrom/MetaData[Key="/image/index"]/Value not found in C:\MININT\Unattend.xml, unable to update.]LOG]!><time="00:56:00.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Updated C:\MININT\Unattend.xml with ImageIndex=1 (value was 1)]LOG]!><time="00:56:00.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[<Message containing password has been suppressed>]LOG]!><time="00:56:00.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Updated PlainText entry to true.]LOG]!><time="00:56:00.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[<Message containing password has been suppressed>]LOG]!><time="00:56:00.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Updated PlainText entry to true.]LOG]!><time="00:56:00.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[//settings[@pass="oobeSystem"]/component[@name="Microsoft-Windows-Shell-Setup"]/UserAccounts/LocalAccounts not found in C:\MININT\Unattend.xml, unable to update.]LOG]!><time="00:56:00.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for Organization]LOG]!><time="00:56:01.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for FullName]LOG]!><time="00:56:01.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for BitsPerPel]LOG]!><time="00:56:01.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for Xresolution]LOG]!><time="00:56:01.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for Yresolution]LOG]!><time="00:56:01.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for Vrefresh]LOG]!><time="00:56:01.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for AreaCode]LOG]!><time="00:56:01.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for CountryCode]LOG]!><time="00:56:01.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for LongDistanceAccess]LOG]!><time="00:56:01.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for LongDistanceAccess]LOG]!><time="00:56:02.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Removed //settings[@pass="specialize"]/component[@name="Microsoft-Windows-Shell-Setup"]/TimeZone from C:\MININT\Unattend.xml because the value was blank.]LOG]!><time="00:56:02.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Removed //settings[@pass="oobeSystem"]/component[@name="Microsoft-Windows-Shell-Setup"]/TimeZone from C:\MININT\Unattend.xml because the value was blank.]LOG]!><time="00:56:02.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for KeyboardLocale]LOG]!><time="00:56:02.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for KeyboardLocale]LOG]!><time="00:56:02.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for UserLocale]LOG]!><time="00:56:02.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for UserLocale]LOG]!><time="00:56:02.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for UserLocale]LOG]!><time="00:56:03.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for UserLocale]LOG]!><time="00:56:03.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for UILanguage]LOG]!><time="00:56:03.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for UILanguage]LOG]!><time="00:56:03.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Updated C:\MININT\Unattend.xml with ImageLanguage001=en-US (value was en-US)]LOG]!><time="00:56:03.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Updated C:\MININT\Unattend.xml with ImageLanguage001=en-US (value was en-US)]LOG]!><time="00:56:03.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Updated C:\MININT\Unattend.xml with ImageLanguage001=en-US (value was en-US)]LOG]!><time="00:56:03.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for Home_Page]LOG]!><time="00:56:03.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for OrgName]LOG]!><time="00:56:03.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for OrgName]LOG]!><time="00:56:04.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for FullName]LOG]!><time="00:56:04.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[No value found for FullName]LOG]!><time="00:56:04.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Updated C:\MININT\Unattend.xml with DestinationDisk=0 (value was 0)]LOG]!><time="00:56:04.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Updated C:\MININT\Unattend.xml with DestinationPartition=1 (value was 1)]LOG]!><time="00:56:04.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Rewrote C:\MININT\Unattend.xml with changes]LOG]!><time="00:56:04.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[ZTIConfigure COMPLETED. Return Value = 0]LOG]!><time="00:56:04.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[ZTIConfigure processing completed successfully.]LOG]!><time="00:56:04.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Event 41001 sent: ZTIConfigure processing completed successfully.]LOG]!><time="00:56:05.000+000" date="07-24-2013" component="ZTIConfigure" context="" type="1" thread="" file="ZTIConfigure">
    <![LOG[Will boot into Windows PE architecture x86 to match OS being deployed.]LOG]!><time="00:56:06.000+000" date="07-24-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[DestinationOSInstallType = BYDISKPARTITION]LOG]!><time="00:56:06.000+000" date="07-24-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Found: DestinationDisk: 0]LOG]!><time="00:56:07.000+000" date="07-24-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Found: DestinationPartition: 1]LOG]!><time="00:56:07.000+000" date="07-24-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[No drive mapped to Disk Partition: \\MININT-IDKMK2C\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="00:56:07.000+000" date="07-24-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Unable to yield a target Partition (Special Recovery option for Litetouch).]LOG]!><time="00:56:07.000+000" date="07-24-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[DestinationDisk and Partition did not yield a target Partition.]LOG]!><time="00:56:07.000+000" date="07-24-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive. See BDD.LOG for more information.]LOG]!><time="00:56:07.000+000" date="07-24-2013" component="LTIApply" context="" type="3" thread="" file="LTIApply">
    <![LOG[Event 41002 sent: FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive. See BDD.LOG for more information.]LOG]!><time="00:56:08.000+000" date="07-24-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Removing AutoAdminLogon registry entries]LOG]!><time="00:56:12.000+000" date="07-24-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[VSSMaxSize not specified using 5% of volume.]LOG]!><time="00:56:12.000+000" date="07-24-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Logs contained 8 errors and 0 warnings.]LOG]!><time="00:56:13.000+000" date="07-24-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[No Windows PE image to delete.]LOG]!><time="00:56:13.000+000" date="07-24-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Stripping BDD commands from unattend.xml template.]LOG]!><time="00:56:13.000+000" date="07-24-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Modified unattend.xml saved to C:\windows\panther\unattend.xml]LOG]!><time="00:56:13.000+000" date="07-24-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Checking mapped network drive.]LOG]!><time="00:56:14.000+000" date="07-24-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[testing drive Z: mapped to \\ncsd-wds.ncsd.local\deploymentshare$]LOG]!><time="00:56:14.000+000" date="07-24-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[testing drive Y: mapped to \\NCSD-WDS\Latitude10Deploy$]LOG]!><time="00:56:14.000+000" date="07-24-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Disconnecting drive Y: mapped to \\NCSD-WDS\Latitude10Deploy$]LOG]!><time="00:56:14.000+000" date="07-24-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Cleaning up C:\MININT directory.]LOG]!><time="00:56:14.000+000" date="07-24-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Cleaning up TOOLS, SCRIPTS, and PACKAGES directories.]LOG]!><time="00:56:14.000+000" date="07-24-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Removing C:\MININT folder (final log entry)]LOG]!><time="00:56:15.000+000" date="07-24-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">

Maybe you are looking for