Mac Delete App Best Practices



That means IT admins can set policies on Mac and Linux machines while AD remains the authoritative IdP. If you would like to know more about the best practices for integrating Macs with Active Directory, drop us a note. You can also sign up for an account and start extending AD today to your Mac fleet. Feel free to contact us if you have any. Resolving The Problem. The following are the best practices that should be employed deleting a user created application in Maximo. To delete an application that you created or duplicated, open a database editor and complete the following steps. Macs also have no way to uninstall or install operating system features, so there’s no way to easily remove the many applications Apple included with your Mac. On OS X 10.10 Yosemite and earlier, it was possible to open a terminal window and issue commands to delete these system apps, which are located in the /Applications folder.

  1. Force Delete App Mac
  2. How To Delete Apps On Windows

Best App Description Practices From the Top 100 Apps

Following up on an earlier study of the top 100 app screenshots, today we analyzed the trends in descriptions of the top 100 apps in the Apple App Store. K lite mega codec pack mac download. Risk 2 free download mac. Below are our summarized & detailed findings, along with additional observations and examples of descriptions lastly. https://spiritualheavy.weebly.com/rapala-pro-fishing-2010-download-pc-crackling.html. If you have any questions, would like to see the raw data or have an idea for a future app store study, please let us know by sending an email to hello@incipia.co.

  1. Being more efficient with the description was the big takeaway, as putting less into the description was correlated with a much better rank across multiple data points:
    1. The longer the app's description, the worse its rank was. It may be that efficiency leads to a better rank, or that the higher ranking apps simply chose to use fewer characters.
    2. Furthermore, it seemed that apps which listed their features out (which can take up a lot of space) did not do too much better than those that did not bother.
    3. Apps that used more contiguous lines in their opening before giving users some white space for breathing room also saw lower average ranks.
  2. Overall, apps that had custom backgrounds did not see a higher rank than those without custom backgrounds.
    1. Editor's Notes-annotated apps which had custom backgrounds ranked worse than those that didn't, but non-Editor-annotated apps with custom backgrounds saw a slightly better rank.
  3. There was a high frequency of, and a higher correlation in ranking for Editor-annotated apps.
  4. Apps that listed quotes from users or PR saw some of the worst ranking differentials.
  5. Including social media links or support contact information were both negatively correlated with rank.

The Data

  • Count of description characters vs average rank. More apps used fewer characters, and these apps had a better ranking than those that opted for longer descriptions.
  • Count of description characters by category. Music and shopping apps used more than half of their allotted description characters, while shopping apps came close; social, productivity and utilities used less than 1,000 characters on average.
  • Editor's Notes? A full 44% of apps had Editor's Notes, which could either be a requirement to be highly ranked, or a function of it. 19/44 Editor-annotated apps had custom backgrounds (average rank 48), while 25 did not (average rank 43). 11/56 apps had a custom background, yet did not sport Editor's Notes (these apps ranked better than non-annotated, non-custom background apps: 53 vs 56).
  • Uses custom background?While 30% of the apps had a custom background, there was no difference in average rank.

Most non-game apps did not see any correlation between opening types, unless they were shopping apps (selling points did best) or games (questions > branding > main value proposition > selling point).

  • Length of opening before white space. When it came to the first five lines of the description (before the 'more' button), there appeared to be value in brevity, up to a point. If apps used three or more lines, they were better off using up all five lines.
  • Bullets types. E.g. Using dots vs dashes.

There didn't seem to be a correlation between using bullets or not (50 with bullets vs 51 without); however, there did seem to be some difference between the types of bullets used, with more and higher-ranked apps choosing classic dots or dashes, vs other bullet types.

  • Features described? Surprisingly, most apps that detailed their features in a manifest way (e.g. 'features list' or listing features of the app without the section header) did not see a better average rank than those that did not (50 with, 51 without). When filtering for non-games, though, feature-descriptive apps saw a small improvement, with an average rank of 47 for describing features vs 50 for not.
  • Provides a 'how it works' section? 9 apps explained how their app worked, yet in vain (average rank 52 with vs 50 without).
  • Use case descriptors? 14 apps used language exploring use cases of their app, with barely any effect (50 with vs 51 without)
  • References user reviews or PR quotes. Astonishingly, this was one of the starkest differences in average rank. The 8 apps that tried to leverage their word of mouth were punished, with collective rank averaging 64, vs 49 for apps that kept mum.
  • Includes social media links? There wasn't an improvement in rank for the 17 apps that added social (52 with vs 50 without)
  • Includes support contact links? Interestingly enough, apps that did not provide a support contact had a better rank than those that did (57 with vs 49 for without).
How to delete apps from macbook pro

Other Observations:

  • Describing premium features was something that many apps did. Many games explained that the game was free to play, but that some items were available for purchase.
  • Some apps, like Cooking Fever and Trivia Crack created a brand persona and used that voice to speak to visitors in terms of 'you' and 'we' (the brand).
  • A good number of apps took the time to inform users of various must-knows, including:
    • Advertising/data collection.
    • The tendency for using GPS to consumes a lot of data battery life.
    • Terms on subscriptions and auto-renewals.
    • Which devices the app was optimized for (or not; Minecraft: Story Mode used its first description line to warn iPhone 4 and 4S users to STAY AWAY). Mentioning iMessage/iWatch/iPad/tvOS compatibility was also common.
    • Links to privacy policies.
  • Curiously, a decent number of apps, like WhatsApp, used CAPITAL LETTERS as their section headers or bullet first words; yet use of symbols to grab attention in the first five lines was limited.
  • Related to the correlation between characters used and rank, many apps focused on describing outcomes, rather than going through all the details of features in the app.
    • Target Cartwheel (See what your friends are saving on).
    • Amazon App (Shop just as you do on the web).
    • Twitter (Join in on all the action by sharing what’s happening in your world).
  • Some apps took to placing social proof, brand slogans and user reviews/PR either at the bottom of the description or after a 2-3 line short description of the app, rather than immediately in the opening five lines, like Venmo and SoundCloud.
  • Some games, such as Clash Royale and Roblox linked to a 'parent's guide.'
  • Several apps also spent a good number of characters name-dropping celebrity, brands and artists, such as Minecraft: Story Mode, iHeartRadio and Hulu.

Description Examples:

  1. Opening description line:
    1. Main value prop – Instagram (Instagram is a simple way to capture and share the world’s moments)
    2. Branding – Snapchat (Life's more fun when you live in the moment :) Happy Snapping!)
    3. Selling point – Pandora (Powered by the Music Genome Project®, the most comprehensive music analysis ever undertaken, Pandora gives you personalized radio that plays what you love and continually evolves with your tastes.)
    4. Question – Juju on the Beat (Can you complete the Juju Running Man Challenge?)
  2. How it Works – Uber:
    1. Requesting your Uber is easy—here’s how it works:
      1. - Just open the app and tell us where you’re going.
      2. - The app uses your location so your driver knows where to pick you up.
      3. - You’ll see your driver’s picture, vehicle details, and can track their arrival on the map.
      4. - Payment can be made by credit card, cash in select cities, Apple Pay, Android Pay, PayPal, and more.
      5. - After the ride, you can rate your driver and provide feedback to help us improve the Uber experience. You’ll also get a receipt by email.
  3. Use cases – Google Maps
    1. Discover places and explore like a local
    2. • Find top-rated restaurants and local businesses, wherever you are
    3. • Decide on the best places to go with reviews, ratings, and pictures of foods and interiors
    4. • Plan your visit and see menus, make reservations, and find when places are typically busiest
    5. • Help others discover the best places by sharing reviews, photos and more
    6. • Save places you want to or often visit, and quickly find them later from any computer or device

That's all for now, folks! Be sure to bookmark our blog, sign up to our email newsletter for new post updates and reach out if you're interested in working with us.

Incipia is a mobile app development and marketing agency that builds and markets apps for companies, with a specialty in high-quality, stable app development and keyword-based marketing strategy, such as App Store Optimization and Apple Search Ads. For post topics, feedback or business inquiries please contact us, or send an inquiry to hello@incipia.co.

Applicable Products

  • Citrix App Layering 4.x

Information

Table of Contents

Operating System Layer

  • Have one Operating System layer per Operating System (Windows 7 32-bit, Windows 7 64-bit, etc)
  • Application and Platform layers are tied to the Operating System layer they were created on.
  • Before a version or layer can be deleted, it must not be in use by a template.
    • You can highlight in the delete pane to see how many templates are using it.
  • After performing an App Layering upgrade, the App Layering drivers, including Elastic, will automatically be updated upon the next publish of a layered image. There is no need to version the Operating System.
    • The scripts that come with each version may be updated. These should be added to the next version you create for your OS layer to patch it.
  • The Operating System layer is always the lowest priority layer. It is always at the bottom of the layer stack no matter what the version date and time is.
  • Hypervisor tools of your main hypervisor should be installed into the Operating System layer.
    • For example, if your main hypervisor is vSphere, you must put the vSphere tools in the OS layer. If you then plan to deploy to XenServer, then those tools are put into the Platform layer.
  • .NET and other Operating System components are best delivered using the Operating System layer.
    • If software has Microsoft components, install those in the OS layer first (for example, the Citrix VDA has Microsoft runtimes as prereq’s. Put those in the OS layer before installing the VDA in the Platform layer).
    • This way you only need to run Windows Updates against one layer.
    • Microsoft Office or other major software from Microsoft is an exception to this rule. Those are best put into Application Layers.
  • Disable Windows Updates using a local GPO as this will work in all Windows Operating Systems
    • Run gpedit.msc change Computer Configuration > Administrative Settings > Windows Components > Windows Update > Configure Automatic Updates > Disable
  • Don’t install applications into the OS layer. The OS layer should be as generic as possible. You cannot swap out the OS layer like you can with App Layers and Platform Layers.
  • Always use KMS for Windows Activation. Run SetKMSVersion.exe when creating your OS layer to configure the startup scripts to activate the correct version of Windows.
  • Any extra user accounts or groups need to be created in the OS layer. Any domain group membership changes need to be done through Group Policy.

Operating System Patching

  • Updating the Operating System should be done by adding a version to the OS layer not a separate layer.
  • If you use any MS products that are updated by Windows Update but don't have a separate section like Office does, include those in the OS layer as well. For example, Windows Defender, Silverlight, runtimes, etc.
  • If in your OS layer the OS says it's not activated then you must reactivate. We provide activation scripts in the c:windowssetupscritpskmsdir folder.
  • Always reboot one more time than the software asks for just to be sure. Should be after disabling updates.
  • If you have hypervisor tools in the OS layer and need to update them, add a version to the OS layer.
    • ​You may also have to recreate your Platform layer due to portions of the hypervisor tools being pulled into the Platform layer.
  • Create a new layered image and TEST

Platform Layers

  • A Platform layer is typically comprised of the provisioning tools, broker tools and domain join. Hypervisor tools may be part of the Platform layer IF it is your secondary hypervisor.
  • The Platform layer has the highest priority when creating the layered image. This means it is applied last so it’s settings will override all other layers.
  • Sometimes an application must be put into the Platform layer. If an application requires interaction with the Single Sign On feature of the broker agent, then that would necessitate putting the application into the Platform layer. For example, Imprivata typically requires this.
  • The Windows security database that holds users and groups is encrypted. Due to this encryption, the database cannot be layered, therefore, domain users or groups added to local security groups are not honored when the layered image is built. For example, domain admins are not in the local administrator group.
    • ​It is best to use Group Policy to populate local groups.
  • If you need to attach extra disks to your Platform Layer for your Provisioning System - for instance, Cache disks or a BDM in PVS - attach them and let Windows detect them and reboot as necessary. When you are ready to Finalize the layer, double-click on the Shutdown for Finalize icon. When the machine is off, remove the extra disks. The Finalize operation from the ELM will fail if there are extra disks on the VM. But don't remove them until Windows is completely shutdown and you are ready to finalize the layer.

Application Layers - Before Install

  • Only use pre-reqs when absolutely necessary for proper application installation
    • To see if an application was installed with a pre-req, click the info box of the application.
  • Per user settings captured in a layer will not be applied to your end users. For example, anything put into the user profile is only captured for the user you logged in as (most cases local administrator)
  • Application layers can be almost anything. They can be files/folders/registry settings that you want delivered to virtual machines, they can be single or multiple applications. There is a lot of flexibility in how you use layers.
  • When creating a new layer, never adjust the “Layer Size” down from the default of 10GB. You can increase the setting if you are packaging a large application.
    • ​ All layers are thin provisioned when stored on the ELM, so even if you are planning on a layer that is very small, never adjust down.
  • Many customers have a utility layer or enterprise application layer that holds the most common components to be delivered to desktops. For example, if Flash, Adobe Reader, and Java are going to be delivered to all/most desktops, then they are put into the same layer.
    • ​ Applications that are updated frequently can also be put in the same layer as well
  • Citrix recommends including the OS Type and OS bit level in the name, for Example Microsoft Office Pro 2010 Win7x32. For versions remember that when choosing a layer, you can see the version name but not the version description. Use naming that will allow you to differentiate versions appropriately. For example, while still in development/testing “1.0 12-12-14-2012 QA ONLY”, but when ready for production “1.0 12-12-2012”.

Installation

  • Turn off automatic updates for applications. If automatic updates are left on, updates may cause issues with the layered image. For example, if an update requires a reboot, this could cause a reboot loop on the virtual machine.
  • When installing an application that requires being part of a domain, it is ok to add the packaging machine to the domain.
    • After installing the application, remove the packaging machine from the domain.
    • Clean up the left-over computer object in active directory

Applications

  • Anti-Virus can be delivered in an application layer or the operating system layer.
    • Citrix Documentation - Deploy anti-virus software has more information on how to configure popular anti-virus solutions with App Layering.
  • Printer drivers can be layered but must be included in the layered image.
    • Local printers are defined in HKLM and will be captured in the layer.
    • Network printers are defined in HKCU and are not captured. Use Group Policy Preferences or login scripts to assign network printers to users.
  • Office can be layered but not elastically delivered. Please see CTX224566 - How to Setup Office with App Layering (Recipe) for information on how to layer Office
    • For additional Office applications (Project, Visio, etc), the base Office layer must be a prerequisite.
    • To keep Office licensing happy, it may be best to create layers for the different combinations of Office plus additional Office applications. For example, a layer with Base + Project, a layer with Base + Project + Visio, etc.
  • We recommend deploying all office applications as part of the layered image, not elastically. This may require several images.
  • .NET is best delivered using the Operating System layer.
  • After a .NET application is installed it is normally required to run the ngen process.
    • Run ‘ngen.exe update’. Do use the ‘force’ switch.

Application Patching

  • Always patch applications as a new version of the application layer
  • Use your latest production OS version with the application patch
  • For Microsoft products like Office, make sure you update the OS layer first to avoid seeing the OS updates when you update Office
  • You will have to enable their update process. If you need to uninstall and reinstall an application or if updating to a new major version of an application, it might be better to create a new application layer. Remember to test this thoroughly because it might affect licensing.
  • Remember to disable the automatic update process before finalizing
  • Remember to clean up any installers or temp directories before finalizing
  • Always reboot one more time than the software says to
  • Always TEST before deploying

Elastic Layers

Force Delete App Mac

  • An application can be applied to the layered image and elastically
    • Do not elastically deliver an application if it’s part of the layered image. For example, if Firefox is part of the layered image, do not deliver it elastically to that image.
  • Consult the Elastic layer log at c:programdataunidesklogsulayersvc.log to troubleshoot Elastic layers and to find the amount of time it took for Elastic layers to be mounted.
  • There is a login hit when attaching an Elastic layer. The amount of time it takes to mount a layer can be seen in the log file.
    • If testing individual Elastic layers, the log in hit is not cumulative. For example, if you test 5 apps individually and it takes each application 2 seconds to mount a layer, that does not mean that it would it take 10 seconds of time to mount all 5 at the same time.
    • There are many portions of the Elastic layer login process that happen only once or are done in parallel.
    • Layers with services will add more time to the logon as the services must be started before the logon is allowed.
  • For virtual desktops, the user will always see the login hit. For Session Host, only the first user mounting the layer will see the login hit. All other users with access to that Elastic layer will log in at regular speeds.
  • Citrix App Layering will help determine if an application can be Elastically delivered. This is called Elastic Fit. Click the ‘i’ on an application and then the ‘+’ next to a version. You will see either a green check or red X. If it’s green, then the application can be delivered Elastically. If it is red, then App Layering has determined that the application may not be a good fit for delivering Elastically. You can then click the ‘+’ sign next to Elastic Fit details to find out why App Layering believes this.
    • This is strictly advisory or best guess. Always TEST a layer before pushing into production.
  • 4k sectors are not supported with Elastic layers.
  • A Highly Available share is highly recommended.
  • It is the USER not the system that is making a connection to an Elastic layer. Setup permissions appropriately.
  • If apps are combined into larger layers there will be less connections to the file server.
  • If Elastic layers are enabled, it will add 20GB to the size of your image for a writable partition.

Maintenance

How To Delete Apps On Windows

  • Before a version or layer can be deleted, it must not be in use.
  • Layer priority is based on creation date and time of the layer. Newer versions will not have an effect on layer priority.
    • Layer priority can be adjusted by using a tool developed by Citrix. This is currently not in the management interface.
  • There is a maximum of 200 layers per layered image.
    • This means there is a limit of 198 Application layers per layered image. -1 for Operating System, -1 for the Platform layer.
  • The ELM storage can be expanded from its initial size. Shutdown the ELM, from the hypervisor expand the disk to desired size, turn on the ELM, from the App Layering management console under System Expand Storage
  • The ELM can be updated without impacting production users. Desktops and Session Hosts connect directly to the share to access Elastic Layers, never the ELM.
  • The ELM requires all tasks to be completed before upgrades can be performed.