Jump to content


sander1975

Established Members
  • Posts

    3
  • Joined

  • Last visited

sander1975's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. please check the logfile using F8 while in your TS (you need to active 'enable debugging' first in SCCM) and go to X: and open the smts.log (C:\Windows\Temp\... ) Then you might see some extra info why the TS is failing. A reason might be that the hash is incorrect, in that case: update distribution point will help.
  2. when you do the same steps you have in your TS by hand (clicking F8 while the TS runs, and go to the correct folder where CCTK is located) and then look in the BIOS (after rebooting the system) is then the TPM step done? When it doesn't your TS is not the problem but either your version of CCTK (do you use the latest version 2.0.1 ?) or the Dell pc itself is the problem. I had the problem with one of my Dell Latitude E6220, updating the BIOS worked in that situation
  3. I have a strange issue at one of my customers. We have SCCM 2012. When I create deployments for a specific collection of users it works fine when the deployments are related to msi packages but when they are coupled with sequences no sequences get installed on the clients. In the SCCM console when I click Monitoring, Deployments and then select the particular deployment with the App-V sequence I see that 'in progress' is the deployment status. When I look at the client which should get the sequence I only see the following in the Virtualapp.log: "The package with GUID ... is not installed on this system yet" although the deployment should install the sequence without user intervention as soon as possible. And in the AppDiscovery.log I see the following entries: '+++AppV package not installed [AppDT ID : ScopeID ....' and the line after that: 'Did not detect app deployment type ... (ScopeID... )' At first I thought the integration between SCCM 2012 and App-V might be the problem, but after reading though the different documents and the chapter 8 of 'Microsoft Application Virtualization Advanced Guide' by Augusto Alvarez, I am quite sure that is not the problem. I also checked the IIS logging to see if some filetypes are not allowed, but nothing strange their too. And read this reference: http://social.technet.microsoft.com/wiki/contents/articles/11447.troubleshooting-application-deployment-in-sccm-2012.aspx, but the boundaries can't be the problem either, otherwise the msi packages (deployments) would fail too in my opinion. Any suggestions where to look or do you have the same issue (and solved it?) ?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.