Ces 2012 update 2.0 android?

is android update available right now or it will be announced later? I read that some updates for native email support and calendar have been announced, but what about android? Will it get updated in february release? Thanks

This will be included in 2.0 release coming this February (hopefully).
BlackBerry Certified Builder for Native Application Development -- Proud member of the Belgian BlackBerry Developer group
Samples: Park in Ghent
Feeling generous? Nominate me for BB Elite member!

Similar Messages

  • Droid 4 unveiled at CES 2012

    My family and I have been waiting to upgrade and sign a new contract for a great phone to come out.  Nothing I have seen yet has really hit the mark to me.  I heard rumors and watched different sites for the Droid 4.  It sounded like it was going to be the phone I was looking for.  
    It has now been unveiled at CES 2012 by Verizon.  It sounded pretty good.  Just what I was looking for.  Slide out keyboard.  4g service.  Dual core processor.  1g ram.  And even a nicer, slimmer look to it.  Then the bomb was dropped.  According to PhoneDog and another site, they are saying that the battery is not removable. 
    With the short battery life of the Android and how often it freezes up, who in their right minds made a Droid where you could not remove the battery? 
    I have the Droid Eris.  From almost day one I have carried a spare battery with me due to the fact that the battery life is so short.  I have had to take my battery out of my Eris at least once a week when it would freeze up on me.
    I don't work in an office where I can just come to work and plug in a phone.  There are some days where I am out for 15+ hours away from any place to plug in a charger.  What in the heck am I going to do to keep my phone charged if the Droid 4 is anything like the Droids of the past? 
    Please Verizon tell me that PhoneDog and the other sites have it wrong.  Please tell me that the battery is removable.  

    For what little bit that I have read on the announced Droid 4, it appears that the battery is not removable. Sorry.

  • Windows Vista is not installing using MDT 2012 update 1

    I have created a media using selection profile in MDT 2012 update 1, but it is not deploying my physical machine. I get error message that Windows Cannot copy files required for installation. Make Sure all files required for installations are available.
    However i have successfully deployed Windows & and Windows XP with MDT 2012.
    I also used different iso image of vista but still i get same error message.

    Looks like you have a *NEW* issue that is unrelated to this thread. Generally I recommend that you open a new thread.
    How to Debug missing Drivers in MDT Litetouch
    I see that you say there are *Problems* but you don't list which devices or drivers are missing.
    From your Bdd.log file I can see that the following drivers are getting copied locally:
    xcopy /seihycd "D:\Deploy\Out-of-box Drivers\Net\e1c60x64_12.6.45.0_63DFBEA09BC1202B9E644652FC90898475BD80F6" "C:\Drivers\Net\e1c60x64_12.6.45.0_63DFBEA09BC1202B9E644652FC90898475BD80F6"
    xcopy /seihycd "D:\Deploy\Out-of-box Drivers\Net\e1c62x64_12.6.45.0_81A271BF21927B572C82D21D23EF89BD7E0ED315" "C:\Drivers\Net\e1c62x64_12.6.45.0_81A271BF21927B572C82D21D23EF89BD7E0ED315"
    xcopy /seihycd "D:\Deploy\Out-of-box Drivers\Net\e1c63x64_12.6.45.0_5B2448F2D9E89D0D8A718B71175BC6A559C8DC6A" "C:\Drivers\Net\e1c63x64_12.6.45.0_5B2448F2D9E89D0D8A718B71175BC6A559C8DC6A"
    xcopy /seihycd "D:\Deploy\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9" "C:\Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9"
    xcopy /seihycd "D:\Deploy\Out-of-box Drivers\System\cdvcore_9.2.2.1039_5676255595E54B75DA4EBCF4BB54B7CBA83C68D4" "C:\Drivers\System\cdvcore_9.2.2.1039_5676255595E54B75DA4EBCF4BB54B7CBA83C68D4"
    However I can't tell what the problem is.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • Update for Microsoft Visual C++ 2012 Update on Windows 7

    I received the Update for Microsoft Visual C++ 2012 Update 4 Redistributable Package (KB3032622).  The installation failed. Here are the details
    Installation date: ‎2/‎10/‎2015 8:35 PM
    Installation status: Failed
    Error details: Code FF
    Update type: Important
    If you use Visual Studio 2012 RTM product to build C++ apps and use certain functionality from the C++ Standard Template Library in your projects, then you might run into a runtime failure similar to the following:
              "The procedure entry point_ crtCreateSymbolicLinkW could not be located in the dynamic link library MSVCR110.dll"
              This was caused due to certain missing function exports in the runtime DLL msvcr110.dll that shipped with VS2012 RTM.  This problem was eventually fixed in Visual Studio 2012 Update 4.  This article
    ensures that the correct runtime DLLs are provided to all users who had previously installed the faulty DLLs from Visual Studio 2012 RTM
    More information:
    http://go.microsoft.com/fwlink/?LinkID=525548
    Help and Support:
    http://support.microsoft.com
    I tried to run the update troubleshooter, but it did not help.  I tried Microsoft Fixit50123, but that did not solve the problem either.
    Little Old Prof

    Hi Little Old Prof，
    I’ve noticed that similar case occurs on this 2/10/2015 update (KB3032622) in some environments. But still a small number.
    And we suggest you run the Windows Update Troubleshooter first and check if there is something need to fix.
    After that please recheck if this update still in your list of updates to be applied.
    Open the Windows Update troubleshooter
    http://windows.microsoft.com/en-us/windows/troubleshoot-problems-installing-updates#1TC=windows-8
    And again, we would appreciate it if you could send us right cbs log file for our reference. Turns out the CBS log you sent to us was ending at 19:01 2/10/2015 and your error occurred at 20:35 2/10/2015.
    Regards
    D. Wu

  • TFS 2012 Update 4 - Build Alert - "A build controller or agent's status changes" doesn't work correctly

    We are running TFS2012 Update 4 and have set up some build alerts.  The alert we have set up is "A build controller or agent's status changes".  When this alert is first set up the default filters which are included are for fields "Team
    Project" and "Status".  However through much testing we have discovered that when either of these fields are included as a filter the alert doesn't work.  When other fields are used in the filter the alert works fine (as long
    as neither of the stated fields are included), indeed if all alert filters are removed then the alert also works successfully.  Has anyone else experienced this?  Is there an issue with the fields "Team Project" and "Status"?

    Hi T Quinn,   
    Thanks for your post.
    I reproduced this scenario in my TFS 2012 Update 4 Server and received the same result.
    For this scenario, please submit it to Microsoft Connect Feedback portal at:
    https://connect.microsoft.com/VisualStudio. Microsoft engineers will evaluate them seriously. 
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • MDT 2012 Update 1 Boot Image Creation Fails in SP1

    I have my site server (SCCM 2012 SP1) installed on Server 2012 with the Windows 8 ADK installed (I've also tried installing the Win7 WAIK with no change to the below problem). It is hosting the site server, FSP, AIS, and Endpoint protection roles. I
    installed MDT 2012 Update 1 (build 6.1.2373.0) and installed ConfigMgr integration. I have a share
    \\siteserver\bootimages that I'm creating the boot image to and the system account has full control on both the NTFS and Share permissions. When I create the boot image I get an error almost immediately and
    a popup that the Microsoft.BDD.ElevatedProxy has stopped working. Details from the pop-up:
    Description:
      Stopped working
    Problem signature:
      Problem Event Name: CLR20r3
      Problem Signature 01: microsoft.bdd.elevatedproxy.exe
      Problem Signature 02: 3.0.0.0
      Problem Signature 03: 50400c36
      Problem Signature 04: System.ServiceModel
      Problem Signature 05: 3.0.0.0
      Problem Signature 06: 4fee6b19
      Problem Signature 07: fb9
      Problem Signature 08: a7
      Problem Signature 09: G3DT0URDW53KGT4VJDEEQCRAUIFCNTLL
      OS Version: 6.2.9200.2.0.0.272.7
      Locale ID: 1033
    The error in the boot image creation wizard is:
    Started processing.
    Creating boot image.
    Error while importing Microsoft Deployment Toolkit Task Sequence.
    System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug>
    configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
    Server stack trace:
       at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
       at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at INewBootImage.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
       at NewBootImageClient.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
       at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)
    I haven't found anything online on this particular error, I've seen all the ones about MDT 2012 and ConfigMgr 2012 CU 1. Any ideas? Any logs that may be revealing to the cause of this error? I've tried removing integration components, uninstalling MDT, reboot,
    re-installing, etc, but same problem occurs each time.

    I just tried to create a new boot image again, the DISM.log file does not show any evidence of the attempt to create the boot wim, in fact nothing since 0800 this morning. The most recent logs are as follows:
    2013-03-03 20:22:59, Info                  DISM   PID=2252 TID=4312 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-03 20:22:59, Info                  DISM   PID=2252 TID=4312 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=4312 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Shutdown SessionTable - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Enter DismInitializeInternal - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Initialized GlobalConfig - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Initialized SessionTable - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2013-03-03 22:02:51, Info                  DISM   API: PID=3544 TID=3672 Waiting for m_pInternalThread to start - CCommandThread::Start
    2013-03-03 22:02:51, Info                  DISM   API: PID=3544 TID=4172 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=4172 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 m_pInternalThread started - CCommandThread::Start
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 Created g_internalDismSession - DismInitializeInternal
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 Leave DismInitializeInternal - DismInitializeInternal
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Enter DismShutdownInternal - DismShutdownInternal
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=4172 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=4172 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2013-03-03 22:03:59, Info                  DISM   API: PID=3544 TID=4172 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2013-03-03 22:03:59, Info                  DISM   API: PID=3544 TID=4172 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=4172 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Shutdown SessionTable - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Enter DismInitializeInternal - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Initialized GlobalConfig - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Initialized SessionTable - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2013-03-04 08:41:08, Info                  DISM   API: PID=1016 TID=1620 Waiting for m_pInternalThread to start - CCommandThread::Start
    2013-03-04 08:41:08, Info                  DISM   API: PID=1016 TID=4176 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=4176 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 m_pInternalThread started - CCommandThread::Start
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 Created g_internalDismSession - DismInitializeInternal
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 Leave DismInitializeInternal - DismInitializeInternal
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Enter DismShutdownInternal - DismShutdownInternal
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=4176 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Shutdown SessionTable - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-05 08:44:10, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Enter DismInitializeInternal - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Initialized GlobalConfig - DismInitializeInternal
    2013-03-05 08:44:13, Info                  DISM   API: PID=4140 TID=3140 Initialized SessionTable - DismInitializeInternal
    2013-03-05 08:44:13, Info                  DISM   API: PID=4140 TID=3140 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2013-03-05 08:44:14, Info                  DISM   API: PID=4140 TID=3140 Waiting for m_pInternalThread to start - CCommandThread::Start
    2013-03-05 08:44:14, Info                  DISM   API: PID=4140 TID=640 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 m_pInternalThread started - CCommandThread::Start
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 Created g_internalDismSession - DismInitializeInternal
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 Leave DismInitializeInternal - DismInitializeInternal
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=640 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Enter DismShutdownInternal - DismShutdownInternal
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=640 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Shutdown SessionTable - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll:                       

  • Xfinity connect 5.2 won't update on my android 4.4 tablet.

    Any idea why xfinity connect won't update on my Android 4.4 tablet?  It is Insight flex 8.  Non rooted standard update tablet.

    As per the Apple iCloud status page, they are having issues. Do not make changes at your end.
    https://www.apple.com/support/systemstatus/

  • MDT 2012 Update 1 - Deployment - Auto Login won't Disable

    Hello,
    I am using MDT 2012 Update 1 with an almost vanilla Windows 8.1 and Windows 7 test box. I can deploy both images fine and get a success on my summary but both machines continue to auto login to the Administrator account. To my understanding, the Auto Login
    should be shutoff via the LTIcleanup script. When I double check the script for the reg keys that are added/deleted I can confirm that this is happening but the images still continue to auto login to the admin account.
    Anyone have any ideas?

    Thought I would let those who are interested know. After speaking with Microsoft Premier Support they determined that you must have a password on the Administrator account. If you don't then something goofs up and causes the auto logon issues that I was
    having.

  • MDT 2012 Update 1 - Attempting to capture Windows Thin PC but it keeps looping after reboot.

    I have been trying to capture a master image of Windows Thin PC we have prepared using MDT 2012 Update 1 but to no avail. When attempting the capture process using LiteTouch.vbs it syspreps and then reboots as it normally would and then it simply keeps rebooting
    over and over in a loop.
    I am unsure of how to bypass this and correctly capture Windows Thin PC using MDT 2012 Update 1. If anyone has any advice or feedback they can offer I would greatly appreciate it. Thank you.

    Logs suggest that the script is most likely crashing early on.
    I suspect that the reason for this is that the deployment share was *updated* from a previous version of MDT, and some files are out of date.
    Can you update the share (full update, regenerate from scratch?)
    Otherwise we may need to run Litetouch.wsf manually from within WinPE:
    When WinPE Boots and you have a mouse, press F8.
    Run TaskMgr.exe and verify that wscript.exe is no longer running (wait 2 minutes).
    Then run the following command:
    "cscript.exe x:\deploy\scripts\litetouch.wsf /debug:true /debugcapture"
    That should run the litetouch.wsf script and it should display any errors if found.
    Keith Garner - keithga.wordpress.com

  • Good am sir i have an problem about may hp touchpad i just update it for android but i am not succes

    good am sir i have an problem about may hp touchpad i just update it for android but i am not success to install it what can i do for it
    This question was solved.
    View Solution.

    Installing another Operating System to your Touchpad is an option with inherent risk, and is not supported here on this Forum.
    Try researching your issue over at http://www.webosnation.com.  They have an entire forum section devoted to "Android on the HP TouchPad".
    WyreNut
    I am a Volunteer here, not employed by HP.
    You too can become an HP Expert! Details HERE!
    If my post has helped you, click the Kudos Thumbs up!
    If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

  • SCCM 2012 updates stuck on device

    Hi all,
    I have problem with SCCM 2012 updates on two machines. I have published security updates on all devices in collections without any problems. Till last week. On two devices, process of downloading has been stuck on 50%, 66% or 78%.
    Could I ask you how I should start troubleshooting this problem (I'm still "new" in SCCM topics).
    Thank you for any ideas and advices.
    Cheers!

    Pls check the logs
    http://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_SU_NAPLog
    Check these discussions
    http://social.technet.microsoft.com/Search/en-US/?query=stuck%20downloading&rq=meta:Search.MSForums.ForumID(7f829d1c-2fc5-4e76-aadc-a118080ff523)&rn=Configuration+Manager+Software+Updates+Management+Forum
    Thanks, Prabha G

  • Slow Imaging on Lenovo T430 with MDT 2012 Update 1

    I am having an issue where laying down the operating system (Custom WIM, Windows 7 x64 about 3GB in size) to a Lenovo T430 machines using MDT 2012 Update 1 is slow.  The install operating system/applying image, seems to hang around 20%, this process takes anywhere from 10-20 minutes to complete before DISM applies the unattend file.  While the process is “hung” the hard drive light on the laptop is solid, so I assume something is going on but I still do not understand why the process seems to hang.  When I image an older Lenovo T410 laptop the WIM is layed down in about in about 5 minutes.  So it seems strange to me that a new laptop model would be slower.  I added new network card drivers and storage device drivers to out of box drivers and updated my deployment share.  I am currently using a lite touch deployment, so I extracted the ISO to a bootable USB stick.
    I thought this was a driver issue but I am not sure now. Anyone else see anything like this? Below is a screenshot of the process I am talking about, although like I said above, it seems to hang around 20% or so.
    Link to picture
    Moderator note; picture(s) totalling >50K converted to link(s) Forum Rules

    I'm experiencing the same issue with our latest batch of T430s laptops, using SCCM 2007 to deploy a custom WIN7SP1 x64 image:
    With the 1st shipment of T430s' we received (Type: 2355-CE8), our image deploys to a system in 31 minutes total. The WIM download + apply stage with this model takes 7 minutes during the deployment.
    With the 2nd shipment of T430s' we received (Type: 2355-2G8), our image deploys to a system in 97 minutes total. The WIM download + apply stage with this model takes 72 minutes during the deployment.
    Aside from an additional stick of memory and a backlit keyboard, these two shipments should've been identical. A quick device manager comparison of the two types shows only one major difference: the Type 2355-CE8 systems use a Micron SSD (C400-MTFDDAK128MAM) where as the Type 2355-2G8 use a Toshiba SSD (THNSNF128GCSS).
    If I swap the Micron SSD (from a Type 2355-CE8 system) into one of the Type 2355-2G8 systems and re-image it, deployment now takes 33 minutes total, and the WIM + download stage takes 8 minutes during the deployment.
    A 2-3 minute difference (total deployment time) is acceptable, but a 60+ minute difference is not.

  • User State Migration Data Capture Failure MDT 2012 Update 1

    Hello All
    Trying to capture data on a Win7 x64 machine so that I can keep the data and restore once the computer is done re-imaging.  This is an offline MDT deployment on the same computer.  See the error below:
    CNAME loop detected. (Error: 000025EB; Source: Windows) 
    Using MDT 2012 Update 1

    Lots of good information out there.  Even stuff that says it's for MDT 2010 also applies to MDT 2012 Update 1 for the most part.  Here's a few to get you started:
    http://deployment.xtremeconsulting.com/2009/11/20/understanding-usmt-with-mdt-2010/
    http://technet.microsoft.com/en-us/magazine/jj127984.aspx
    http://blogs.technet.com/b/mniehaus/archive/2009/07/01/mdt-2010-new-feature-12-usmt-4-0-hardlink-support.aspx
    http://www.windows-noob.com/forums/index.php?/topic/3758-usmt-mdt/
    http://channel9.msdn.com/Events/MMS/2013/DC-B301 (great video with Johan presenting, focused on USMT 5.0)
    You should create a default Standard Client Task Sequence and look at the State Capture and State Restore groups to see what MDT sets up for you by default that you may have removed from your current Task Sequence.  But the direct answer to your question,
    is that ScanState (part of USMT) is the part that creates a backup.  LoadState is the piece that restores it to a machine.
    David Coulter | http://DCtheGeek.blogspot.com |
    @DCtheGeek

  • USMT 4 Wrong version error - MDT 2012 update 1

    Hi,
    we are in process of Migrating XP to windows 7, i have prepared a media using MDT 2012 update 1 and WAIK,
    When i started deployment using the DVD i am getting the following error message
    " The USMT Files in e:\..\..\x86\USMT4 are the wrong version. failure 9701.
    When i checked in the above mentioned path i can see the USMT 4 folder with all required files inside it and i even compared the folder with USMT4 folder of c:\program files\WAIK instllation folder and i did not find any difference between them.
    When i tested the deployment from the share folder by accessing (\\itd-mig\deploymentshare$) i was able to migrate without any error.
    Can any one help me to find out what is the error about.
    Thanks in advance.
    D. Sendil Kumar

    Ugh...
    ValidateCaptureLocation is a function in the Deployment Wizard, the wscript object is *not* available from within the MSHTA environment, so be careful.
    Instead of:
    wscript.sleep 5000
    use this instead:
    outility.SafeSleep 5000
    Is your DHCP server slow?
    Keith Garner - keithga.wordpress.com

  • Deploy windows8 with custom partition using MDT 2012 update 1

    Hi,
    I am deploying windows 8 using MDT 2012 update 1 on SCCM 2012. I want C drive (to be quick format using task sequence) and D drive (remains same) on new system. While using diskpart , my D drive always get format . Can anyone suggest the steps.
    Regards
    Manish

    Hi,
    You could try steps in the following blog.
    http://arnavsharma.net/4/post/2014/02/mdtformatting-only-c-drive-during-upgrade.html
    (Note: Microsoft provides third-party contact information to help you find technical support. This contact
    information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.)
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

Maybe you are looking for

  • Número de protocolo de NF-e

    Boa tarde! Implementamos o processo de NF-e em nosso cliente e estamos com a seguinte dúvida: - uma NF-e é enviada para a Sefaz (processo SD) e autorizada; - em um segundo momento essa NF-e é cancelada e o seu cancelamento autorizado. Em paralelo é c

  • Console reporting webkit having hundreds of wakeups per second

    I have been noticing frequent computer slowdowns on my 2011 MacBook Pro, always fully patched. Checking Console, I found dozens of reports from Webkit saying things like "140 wake ups per second for 194 seconds" I think these are related!!!  Can some

  • Some SD popular TV shows now come in 5.1 surround sound!

    I just realised that some Standard Definition (SD) popular TV shows like Prison Break and Heroes now come with 5.1 surround sound. Thanks to my sound equipment. Usually, I will see sound indicator displaying PCM. Was doing a preview of the two above

  • Recording audio without video

    Is there any way to record live audio from a mic and streaming it through FMS without having to have a webcam plugged in? Is there way to use another video source other than a webcam, such as an existing flv? thank you.

  • Beginner needs help -- viewer disabled for capture

    I am trying to capture from a dvcam. When I first open FCP says there is no connection - even if i retry, no conneciton. When i go to capture, even when it does read dvcam (VTR ok) there is no preview - just color bars. Have tried resetting system pr