Jump to content


Ath3na

Established Members
  • Posts

    50
  • Joined

  • Last visited

  • Days Won

    6

Posts posted by Ath3na

  1. If you are using the application model to deploy applications then if the application is already on the machine the application detection rule will detect the software already present. This will then mark the deployment as success but the application will not attempt to re-install the software.

     

    You can migrate from SCCM 2007 / 2012 to 2012.

    You could migrate all your applications/packages/images/collections, then clients.This way all your old figures for deployment would be carried across to the new SCCM installation and you can continue from where you left off.

    • Like 1
  2. Might be worth doing your testing under the system account

    Grab psexec from the internet (pstools) and do a psexec -i -s cmd.exe

    This should open a second cmd window.

    Whoami

    should show the system account.

    Test.

     

    Why does the uninstall cause explorer to close?

    Sometimes windows installer will behave differently if run with /qb instead of qn.

     

    If you log the uninstall of the MSI is there anything relevant in the log file?

     

    Does the application close explorer if you remove it via programs and features?

  3. You could have a look at the MSI property table to see if there are any public property's you can set, anything in upper case.

     

    Sometimes the Vendor doesn't provide something built in, and you have to edit the MSI via a transform and remove the shortcuts.

    be-Careful of removing advertised Shortcuts as these will sometimes be adding in some missing component for other users.

     

    Sometimes I use a custom action VBScript to clean up shortcuts. You could just add something like this to your wrapper.

    Here are some examples.

     

    set wshShell = CreateObject("WScript.shell")
    set FSO = CreateObject("Scripting.FileSystemObject")
    
    DesktopPath = wshShell.SpecialFolders("AllUsersDesktop") 
    shortcut = DesktopPath & "\Sage 50 Accounts 2012.lnk"
    
    If FSO.FileExists(shortcut) Then
    FSO.DeleteFile shortcut
    End If
    
    dim strProgramData, strapppath
    
    set wshShell = CreateObject("WScript.shell")
    set FSO = CreateObject("Scripting.FileSystemObject")
    
    strProgramData = wshShell.ExpandEnvironmentStrings("%ProgramData%")
    strapppath = strProgramData & "\Microsoft\Windows\Start Menu\Programs\Sage Accounts"
    
    if FSO.FolderExists(strapppath) then
    FSO.DeleteFolder(strapppath)
    end if
    
    
  4. There might not be an issue.

     

    When you go to distribute content it will only show you distribution points that do not already have the software.

     

    Check the content tab of the distribution point properties. From here you can see what is cached and can remove applications.

    If you remove an application from the DP then go back to the wizard it will allow you to distribute to that server again.

     

    It doesn't sound like you have an issue.

  5. You could create a collection of all devices without .netframework 4.5

    You could then send out the .net installer to those remaining machines.

     

    This would ensure all devices have the pre-req.

     

    Another option - instead of creating a package for the dotnet installer you could create a deployment using the newer application model.

    This will then have a detection method. You wouldn't then have to worry about if dotnet is installed or not as the application model detection method first checks to see if the software is installed and if it is marks the deployment as already compliant, nothing else happens.

    If the detection method is not compliant then the install runs and makes it compliant.

  6. Has the server had a reboot lately?

    Anything in eventvwr?

    Any problems in monitoring of your site / components?

     

    I recently stopped using the in built task to create a back up after reading this.

    https://stevethompsonmvp.wordpress.com/2013/06/07/sql-server-backup-recommendations-for-configuration-manager/

     

    My site back up was getting pretty big, there is a huge size difference with backing up directly in SQL.

  7. Hi,

     

    Find your device in the 'All Systems' Collection

    Right click your client - properties.

    Check the deployment tab - is kodu / xna listed?

     

    Is this deployed as an application or package?

    if an application check C:\Windows\CCM\Logs\appenforce.log on your client.

     

    http://blogs.technet.com/b/configmgrdogs/archive/2012/05/26/new-logs-in-configmgr-2012-client-logs.aspx

     

    If it's deployed as a package check the execmgr.log in the same location on the client.

     

    To make log files easier to read use cmtrace.

    https://sccmentor.wordpress.com/2013/06/27/cmtrace-log-viewer-for-sccm-2012/

     

    Just open trace from your client then open any log file :)

  8. Have a look at the properties of each client to see what type of discovery is discovering them and take it from there.

     

    This WQL query will show you all duplicate devices, yes you can remove the device

    select R.ResourceID,R.ResourceType,R.Name,R.SMSUniqueIdentifier,R.ResourceDomainORWorkgroup,R.Client from SMS_R_System as r   full join SMS_R_System as s1 on s1.ResourceId = r.ResourceId   full join SMS_R_System as s2 on s2.Name = s1.Name   where s1.Name = s2.Name and s1.ResourceId != s2.ResourceId
    
  9. I have seen a lot of sites with configuration manager installed to the OS drive and not had any specific issues. IIS logs sometimes tend to take up lots of space but 150 free GB is a lot of space for a windows volume.

    You could move the content library to another drive, there is a tool that lets you do this.

    http://blogs.technet.com/b/neilp/archive/2013/01/08/configuration-manager-2012-sp1-content-library-transfer.aspx

  10. If these are MSI's you can use the product code of the application.

     

    When creating the detection method there is an option for MSI, browse to the MSI and it will automatically find the product code for you.

    Another option would be to find the product code in the registry.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

     

    Or you could use something like ORCA to find the details in the property table.

     

    If you are not using an MSI you could use a rule to find an existing file or reg key or folder.

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