Driving Openness & Innovation Through the Modern Computing Alliance

We’re living through a time of rapid transformation—where technology that helps us connect, collaborate and communicate has taken center stage. We’ve been talking about this period as the “Renaissance of the PC”, where we have a unique opportunity to think and do differently to drive better customer experiences. This “renaissance” doesn’t only apply to the device itself, but how the broader computing ecosystem can come together to drive modern experiences.

Today we’re doing just that with the Modern Computing Alliance. We’ve joined as a proud founding member, alongside Google, Intel, VMware, Citrix and many other members.

What is our goal with the Modern Computing Alliance? It’s simple: to drive an open and innovative ecosystem so customers can get the most from their Chrome OS experiences.

Take our Latitude Chromebooks as an example. We already give IT departments the flexibility to easily integrate the Chrome OS into their ecosystem while still enjoying the global availability, scale and features that our Latitude devices offer.

The Modern Computing Alliance will further build on this idea.

We will collaborate with everyone from software partners to Silicon Valley start-ups to drive more value and innovation for Chrome OS in the broader IT ecosystem. Looking beyond devices, we’ll explore things like data security, insights and multi-factor authentication to create more value and innovation for people like you and me. People that use our devices every day.

If there’s anything I’ve learned this year, it’s that our diverse viewpoints and collective strengths can bring about amazing changes – a “renaissance” – for customers and for ourselves. Our goal for our work with the Alliance is that we bring even more innovative, flexible experiences to you. Learn more here.

    Related:

    • No Related Posts

    Users are Unable to Start published apps as they recieve launch.jsp instead of launch.ica

    There are some generic rewrite policies which support the following platforms:

    • iPhone Receiver
    • iPad Receiver
    • Android Receiver
    • Blackberry Receiver
    • Mac Receiver

    List of generic rewrite actions

    • add rewrite action replaceLocationJspToIca replace “HTTP.RES.HEADER(“Location”).REGEX_SELECT(re#/site/launch.jsp#)” “”/site/launch.ica”” -bypassSafetyCheck YES
    • add rewrite action replaceLaunchUrlIcaToJsp replace “HTTP.REQ.URL.PATH.REGEX_SELECT(re#/site/launch.ica#)” “”/site/launch.jsp”” -bypassSafetyCheck YES
    • add rewrite action replaceContentType replace “HTTP.REQ.HEADER(“Content-Type”)” “”application/x-www-form-urlencoded”” -bypassSafetyCheck YES
    • add rewrite action insertXmlDocument insert_before “HTTP.REQ.BODY(6).SUBSTR(0,1)” “”xmlDocument=”” -bypassSafetyCheck YES
    • add rewrite action replace_launch_jsp_in_body replace “http.RES.BODY(5000).REGEX_SELECT(re#launch[.]jsp#)” “”launch.ica””

    List of generic rewrite policies

    • add rewrite policy rw_wi_302_by_ipad_iphone “(HTTP.RES.STATUS.EQ(302) || HTTP.RES.STATUS.EQ(200)) && HTTP.REQ.URL.SUFFIX.EQ(“jsp”) && (HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“iPad”) || HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“Safari”) || HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“iPhone”)) && HTTP.RES.HEADER(“Location”).CONTAINS(“/site/launch.jsp?CTX_UID=”)” replaceLocationJspToIca

    If the above expression does not work,change it to:

    (HTTP.RES.STATUS.EQ(302)) && (HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“iPad”) || HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“Safari”) || HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“iPhone”)) && HTTP.RES.HEADER(“Location”).CONTAINS(“/site/launch.jsp?CTX_UID=”)

    • add rewrite policy rw_wi_launch_ica_by_ipad_iphone “HTTP.REQ.URL.SUFFIX.EQ(“ica”) && (HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“iPad”) || HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“Safari”) || HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“iPhone”)) && HTTP.REQ.URL.PATH_AND_QUERY.CONTAINS(“/site/launch.ica?”) && HTTP.REQ.HEADER(“Cookie”).CONTAINS(“JSESSIONID=”)” replaceLaunchUrlIcaToJsp

    If the above expression does not work,change it to:

    HTTP.REQ.URL.SUFFIX.EQ(“ica”) && (HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“iPad”) || HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“Safari”) || HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“iPhone”)) && HTTP.REQ.URL.PATH_AND_QUERY.CONTAINS(“/site/launch.ica”) && HTTP.REQ.HEADER(“Cookie”).CONTAINS(“JSESSIONID=”)

    • add rewrite policy rw_wi_posthdr_by_receiver “HTTP.REQ.METHOD.EQ(POST) && HTTP.REQ.URL.SUFFIX.EQ(“jsp”) && (HTTP.REQ.URL.PATH_AND_QUERY.ENDSWITH(“enum.jsp”) || HTTP.REQ.URL.PATH_AND_QUERY.ENDSWITH(“launch.jsp”)) && HTTP.REQ.BODY(6).STARTSWITH(“<?xml “)” replaceContentType
    • add rewrite policy rw_wi_postbody_by_receiver “HTTP.REQ.METHOD.EQ(POST) && HTTP.REQ.URL.SUFFIX.EQ(“jsp”) && (HTTP.REQ.URL.PATH_AND_QUERY.ENDSWITH(“enum.jsp”) || HTTP.REQ.URL.PATH_AND_QUERY.ENDSWITH(“launch.jsp”)) && HTTP.REQ.BODY(6).STARTSWITH(“<?xml “)” insertXmlDocument
    • add rewrite policy rw_wi_200_by_ipad_iphone “HTTP.RES.STATUS.EQ(200) && HTTP.REQ.URL.CONTAINS(“launcher.jsp”) && (HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“iPad”) || HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“Safari”) || HTTP.REQ.HEADER(“User-Agent”).CONTAINS(“iPhone”)) ” replace_launch_jsp_in_body

    Related:

    When Enrolling iPad using Enrollment Invitation wrong profile is downloaded and enrollment fails

    It is recommended to use the iOS URL (platform = iOS).

    Safari on iPad devices, now reports itself as a macOS device.

    Citrix Endpoint Management site has no option to redirect to the correct iOS site, before the browser will redirect to the right web page. As a result, the wrong profile is downloaded.


    When enrolling an iPadOS device using the iOS URL (i.e. https://serverFQDN:8443/instanceName/ios/otae), the following message will be displayed. Please ignore the message and enter credentials to enroll

    Note:Enrolling using OTA URL is not supported anymore for iPadOS and iOS (only for macOS)

    Related:

    Can the Symantec SEP for Mobile be used to deploy the unfied agent to Android devices?

    I need a solution

    Hi;

    Can the Symantec SEP for Mobile be used to deploy the unfied agent to Android devices? My understanding is that it cannot. However, though I would double check.

    For IOS devices, what is needed other than deploying the SEP mobile solution on all Ipads or iphones?

    Kindly

    Wasfi

    0

    1554441077

    Related:

    “Unable to download app” with Enterprise .ipa Application and XenMobile

    There could be an issue with the .ipa file, therefore iOS will reject the installation, we see “The provisioning profile has expired”.

    Or

    The issue could be because the ipa file is from App Store and still encrypted.

    Or

    The application is using adhoc profile and the adhoc profile doesn’t have testing device’s udid included

    We found the following lines in the logs:

    Jan 30 13:05:07 mdms-iPad misagent[93] <Notice>: MIS: attempt to install invalid profile: 0xe8008011

    Jan 30 13:05:07 mdms-iPad installd[47] <Error>: 0x16e12f000 -[MIInstallableBundle _installEmbeddedProfileInBundle:]: Could not install embedded profile: 0xe8008011 (This provisioning profile has expired.)

    Jan 30 13:05:07 mdms-iPad securityd[87] <Error>: secTaskDiagnoseEntitlements MISSING keychain entitlements: no stored taskRef found

    Jan 30 13:05:07 mdms-iPad securityd[87] <Error>: secTaskDiagnoseEntitlements MISSING keychain entitlements: no stored taskRef found

    Jan 30 13:05:07 mdms-iPad installd[47] <Error>: SecTrustEvaluate [leaf IssuerCommonName SubjectCommonName]

    Jan 30 13:05:08 mdms-iPad installd[47] <Error>: 0x16e12f000 +[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:]: 142: Failed to verify code signature of /private/var/mobile/Library/Caches/com.apple.mobile.installd.staging/temp.Pjgwlp/extracted/Payload/RMApp.app : 0xe8008015 (A valid provisioning profile for this executable was not found.)

    Jan 30 13:05:08 mdms-iPad installd[47] <Error>: 0x16e12f000 -[MIInstaller performInstallationWithError:]: Verification stage failed

    Jan 30 13:05:08 mdms-iPad itunesstored[207] <Error>: 0x16e35f000 __MobileInstallationInstallForLaunchServices_block_invoke222: Returned error Error Domain=MIInstallerErrorDomain Code=13 “Failed to verify code signature of /private/var/mobile/Library/Caches/com.apple.mobile.installd.staging/temp.Pjgwlp/extracted/Payload/RMApp.app : 0xe8008015 (A valid provisioning profile for this executable was not found.)” UserInfo={LibMISErrorNumber=-402620395, LegacyErrorString=ApplicationVerificationFailed, SourceFileLine=142, FunctionName=+[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:], NSLocalizedDescription=Failed to verify code signature of /private/var/mobile/Library/Caches/com.apple.mobile.installd.staging/temp.Pjgwlp/extracted/Payload/RMApp.app : 0xe8008015 (A valid provisioning profile for this executable was not found.)}

    Jan 30 13:05:08 mdms-iPad itunesstored[207] <Warning>: ERROR: MobileInstallationInstallForLaunchServices returned nil

    Jan 30 13:05:08 mdms-iPad lsd[192] <Warning>: LaunchServices: Setting progress = FAILED for app com.axis.rmApp

    Jan 30 13:05:08 mdms-iPad itunesstored[207] <Warning>: LaunchServices: installPhaseFinishedForProgress: com.axis.rmApp.Installing – <NSProgress: 0x156de10b0> : Parent: 0x0 / Fraction completed: 0.0000 / Completed: 0 of 100 called, removing progress from cache

    Jan 30 13:05:08 mdms-iPad itunesstored[207] <Warning>: [ApplicationWorkspace]: Failed to install application: com.axis.rmApp; /var/mobile/Media/Downloads/6431870034647236558/9172328357785919310; Error Domain=LaunchServicesError Code=0 “(null)” UserInfo={Error=ApplicationVerificationFailed, ErrorDetail=-402620395, ErrorDescription=Failed to verify code signature of /private/var/mobile/Library/Caches/com.apple.mobile.installd.staging/temp.Pjgwlp/extracted/Payload/RMApp.app : 0xe8008015 (A valid provisioning profile for this executable was not found.)}

    It could be the .ipa provisioning profile has expired and needs to be renewed.

    Related:

    How to Integrate XenMobile with Apple Education Feature

    With iOS 9.3, Apple made significant enhancements for schools and institutions. They delivered the following key enhancements:

    ·Apple School Manager (ASM)

    ·Classroom app

    Apple School Manager (ASM) is a new web portal that unifies DEP and VPP portals at the same place. It allows the admin to:

    • Assign DEP devices to different MDM servers:
    • Purchase VPP licenses for App Store’s apps and iBooks.
    • Create and manage Apple IDs in bulk (Managed Apple IDs) for the school to access to Apple services (iTunes and App Stores, iBooks, etc.), including storing documents in iCloud Drive and enrolling in iTunes U courses.

    Classroom app is a new free app available in iOS 9.3 and later on the App Store that gives teachers a tool to manage and guide remotely the student’s devices. This app uses Bluetooth or Wi-Fi to establish a connection between the teacher’s iPad and the student’s iPad. It works in both one-to-one and shared devices and is configured with MDM. To set up, the MDM server should push an Education Configuration policy to the teacher’s iPad. This policy defines the list of classes, students and departments that the teacher could manage:

    • Launch the entire class into a specific app.
    • Share and open a link to a website.
    • Open and lock an app.
    • Present a student’s work via Apple TV.

    Related: