Client Auto-Update questions

We just updated our Dev system to SP5 with Patch 2, but the clients are not updating automatically.
I have checked that the Client and Admin boxes are checked for auto-update and can see nowhere else that this can be done.
I double-checked with the Master Install guide, and this appears to be the only thing that I need to do to make it work.
The clients are currently at 502, and they should now be 506.
Also, is this controlled by the files in C:\BPC\Websrvr\Web\Installation?
I have checked the live server (BPC 5.1 SP3) and the Dev server (BPC 5.1 SP5r2)
Both of them have EverestClient.exe and EverestAdmin.exe with version number 12.0.0.49974
Does that seem right?  I would have expected an increment in version number.
Has anyone else seen this, and can you offer any advice?
Thanks
Craig
Edited by: Craig Aucott on Feb 23, 2009 9:46 AM

Here is an extract from the note:
It does not say about the Patch! sorry...
the note is 1269662
Summary
Symptom
The Client Auto Update feature does not work in 5.1 SP5.
Other terms
auto, update, client, upgrade, install
Reason and Prerequisites
This is due to unintended consequences of fixing IM 3569686 issue in SP5.
Solution
Remove the '<remove name="Documentation"/>' node from the web.config file located in the x:\bpc\websrvr\web directory and save.
Once all clients have been updated, add the node back to the file.
The node is found in the following section:
<globalization requestEncoding="utf-8" responseEncoding="utf-8"/>
  <webServices>
       <protocols>
            <add name="HttpSoap"/>
            <add name="HttpGet"/>
            <add name="HttpPost"/>
            <remove name="Documentation"/>
        </protocols>
  </webServices>
Header Data
Release Status:     Released for Customer
Released on:     25.11.2008  19:51:41
Master Language:     English
Priority:     Correction with high priority
Category:     Program error
Primary Component:     EPM-BPC-MS-SVM-OTH Other
Hope this helped
Bye

Similar Messages

  • Hierarchy auto update & auto push client question

    I just upgraded to 2012 R2 and needed to upgrade everyone's client. I first started with the hierarchy auto update setting, but then enabled the client push setting as well. Can these two settings be enabled at the same time, or will this cause client
    errors?

    yes they can be enabled at the same time.
    From the technet: Automatic client upgrades are useful when you want to upgrade a small number of client computers that might have been missed by your main client installation method (client push installation). For example, you have completed an initial client
    upgrade, but some clients were offline during the upgrade deployment. You then use this method to upgrade the client on these computers when they are next active.
    Thanks!

  • What is the last question at the end of auto-updates? "Allow" what? (I clicked on "Done" too fast.)

    Hi, I installed an auto-update today, lazily clicked on "Done" at the end without taking the time to read the last "pop-up" dialog box. I saw options about "allowing" something but I did not get a chance to read the question before it disappeared. What was that last question???

    replying to JS1111
    Now I only get one HKEYLOCALMACHINE\Software\
    QuicktimePlayerLib.QuicktimePlayerApp\CLSID.
    some folks have been having some success with pgfpdwife's technique in the following post:
    pgfpdwife: Re: Could not open key HKEYLOCALMACHINE\Software\Classic\Quicktime.Quicktime\
    note carefully that the technique involves a registry edit. be sure to make a backup of any keys you edit. if you're unfamiliar with your registry or registry editing, head to your XP help and support, do a search on registry, and read through the articles that come up.
    There are also some instructions on how to back up registry keys in the following document:
    Error 1406 or 1402 appears when you install iTunes or QuickTime for Windows

  • Auto-update waking computer from sleep question.

    Will the computer awake from sleep at the prompting of auto-update?
    Thank you.

    Hi, and welcome!
    I very much doubt that the computer would wake from sleep. If my understanding is correct, the auto-update feature works by just checking every now and then if there are any updates available. It cannot perform this check while it is sleeping.
    So, I think I can safely say that the answer is: no.

  • SUN .... When....  JRE 1.4.0 international with auto update

    SUN .... When.... JRE 1.4.0 international with auto update
    When will you deliver .........
    We have a dead line and our product needs the international version 1.4 to be updated on our exsiting user base, one of our customers has over 700 workstations.
    If the solution is to manually dowload and install this version then Web Start totally fails as a web centric solution.
    I see that creating our own servlet breaches SUN's license agreement, so give us a developer servlet we can use.

    The auto download servlet supports both international and us-only versions of Java 1.4.0.
    Java Web Start includes the current locale in the request to the servlet, and it returns the
    US only version if the locale is en_US , or the international version otherwise.
    Curently there is no way to get the servlet to download the international version when the
    clients locale is en_US.Sorry but havent you just anwsered the question I put, either the servlet supports international clients or it dosent and your anwser just puts more wood on the fire, it dosent, but it could.
    Also we recognize that there is a problem when an application needs the international version, and >>the client already has the US version installed. In this case Java Web Start will not attempt
    to contact the servlet since it thinks it has an appropriate version allready.Also if you client requires an international version of the JRE it is because it requires that version period, hence if the version tag within the JNLP file specifies JRE1.4 international, then it dosent matter what Web Start may or may not think, the JNLP file written for the application by the author should determine its fate.
    The only reason Web Start should determine locale on a target machine would be the text displayed for the dialog interface between the end user.
    Its a simple case of checking do I have 1.4 international, "Yes or No", at this point I dont care if 1.4 English is installed, or locale is English, JNLP file asked Web Start, if 1.4 international was installed, "No", Ok then call servlet and request 1.4 international. Simple....
    The JRE license agreement allows customers to repackage and redistribute the JRE.
    Many customers are redistributing a JRE with their app. Im sure many are, please read my previous post , if you can get sun to offically confirm this, then I stand corrected.

  • Enabling Silent Auto-update in Java 7.45 as a non-local administrator user, enterprise best practices?

    So I have been looking through forums, java help, and everywhere possible for more insight on java in an enterprise environment. What I have found so
    far is that there is no actual way to enable auto updates to install as a non-local admin user.
    I know you can turn on and off updates My company wants to install java JRE as a silent-autoupdate "always update" kind of installation, but all my users are domain users, without admin rights. When it finds an update - it prompts for credentials and obviously they are denied. Is this even possible?  If it is not possible to "auto-update" non local admins, I can make the case to management that java releases need to be QA'd and controlled releases. My environment is adminstudio/installshield and SCCM. I know auto-installing updates to java without QA per version , in a enterprise environment, is not good practice, but its not my decision right now.
    thank you very much!

    Hi and thank you very much for responding!
    I'd be interested in further answers:
    Our company is developing unsigned applets ...Why?Sufficient functionality. We dont want to e. g. access the customers local file system, we just wanted to use the applet as viewer sending data to and from the server where the applet was loaded from. Nothing else.
    1. What is the idea to show messages for unsigned applets running in a secure sandbox.. why when running in a sandbox, and why not also for potentially more dangerous signed applets?With a signed applet you know who is taking the responsibility.With unsigned applets, I rely on the sandbox responsibility. I actually couldn't do anything dangerous by accident.
    With signed applets, I'm fully responsible that nothing bad happens to the clients data. Preventing this is the main task for the java sandbox, so why not use it?
    Just to clarify: Is it right that each signed applet has full access rights?
    3. Is there any recommended strategy to sign an applet to work across browsers, platforms, JRE versions?Err, sign it?Does the signing scheme matter? According to http://mindprod.com/jgloss/signedapplets.html, there are lots of...
    Could you recommend a good tutorial? I'm an absolute beginner concerning signing of applets.
    4. Are there negative side-effects to sign an applet?Only that it forces you to sign all its components. Not sure what this question means.What about loading time and jar filesize?
    Does JarIndex work with multiple signed modular applet jars?
    Must javascript code also be signed to talk to signed applets?
    Is a client able to see a signed applet a) without see or interact with a confirmation window and b) without doing any prerequisites (like adding certificates or similar)?
    Thanks, Peter

  • Must be Auto update flash Player/AIR [No update alert]

    Every second day Adobe are improving the flash player and AIR, so Flash Player must be Auto update to newer versions and (Major and minor) [No update alert]. It should auto check, and auto download and auto update the flash player. There should not be any user interaction needed. And no administration rights as Flash player is already installed on system, Adobe is just auto updating it. So no alert or dialog box to update player just auto update with out any message as Google Chorme is doing right now (Google chrome update the browser application without any alert to user). So Please follow it.
    Why it's required: Every second day Adobe programmers are improving and adding new features, but Flash/Flex developers around the globe can not use those features as their target customers (users) don't have the updated version of flash player/AIR. We can show the alert but we know most of users pick the "NO" as their preferred option.
    How can Adobe implement this, there are privacy issue: Adobe can implement this by changing their Adobe flash player agreement (for new installations). They can add one "Flash player policy" web page to their website and link at their home page. Adobe can add one more menu element in their setting tab (right click flash player menu). It's will take little time but for future, it will be really easy for developers to adopt the new feature and software from Adobe.
    Please think about it.

    Hi ersatyle,
    Thanks for clarifying.
    will flash player  be automatically updated while a standard user is connected (no admin rights) and without any notifications.
    By pointing the Background Updater to an internal server, yes.
    Are those settings will work as I intended?
    The AutoUpdateInterval setting in the mms.cfg has no effect on the Background Updater. AutoUpdateInterval can only be used for the notification updater. If you're setting up background updates from an internal server, this property is best dropped from the mms.cfg to avoid confusion. The other settings will work as expected. Once you have your clients set up and tested, I also recommend dropping SilentAutoUpdateVerboseLogging, since this will reduce the size of the log file.
    As we'll use 32 bits browsers do I need to put the mms.cfg file also in c$\Windows\System32\Macromed\Flash, If it wont work, is it doable?
    There is only one location for the mms.cfg. The same file is used for 32-bit and 64-bit browsers. From the administration guide, page 22:
    mms.cfg file location:
    Assuming a default Windows installation, Flash Player looks for the mms.cfg file in the following system directories:
    •32-bit Windows - %WINDIR%\System32\Macromed\Flash
    •64-bit Windows - %WINDIR%\SysWow64\Macromed\Flash
    Note: The %WINDIR% location represents the Windows system directory, such as C:\WINDOWS.
    I hope this answers your questions. Let us know if there's anything else.
    -Stephen

  • How do I roll-back to the previous version of Firefox? An auto update occurred and now one of the programs used at the office (ACT! v6.0 SwiftMail) won't run with the browser.

    The office I work in uses a very old version of ACT!, an accounting package. This package has a component called SwiftPage, an antiquated email system that enables us to email from the ACT DB. SwiftPage runs via the web browser.
    Firefox just did an auto update (that I will have to find out how to turn off) and now SwiftPage won't run as it is not compatible.
    Can I "roll-back" my version of Firefox or do I have to uninstall and try to re-install an older version?
    HELP!

    Try loading and using the add-on from this link: https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/
    Many add-ons do in fact work if you force them to run. The procedure to roll-back is given in this article: [[installing previous versions of firefox]]
    Unfortunately the official Firefox policy is that you downgrade to 3.6 which is supported for a while longer, and not the now unsupported Firefox 4. If after installing and running the ''add-on compatibility reporter'' you still have problems there are ways around the official policy.
    I think it is absurd that Firefox 4 may be used by tens of millions of users one day and a few days later those that upgrade to Firefox 5 should be not only told not to use a now unsupported browser, if they need to revert due to problems, but are actually obstructed in attempts to do so. See also [/questions/840397#answer-205154]

  • How to disable yum auto-update in OL6

    Hello,
    What is the correct procedure to disable yum auto-updates?
    The "yum-updatesd" daemon that existed in OL 5 does no longer exist in OL 6.
    I found out that the "PackageKit Update Applet" seems to be responsible for running the auto-update. It can be enabled or disabled in the new Preferences/Startup Applications control panel. There is also the "gpk-prefs" control panel to set the update interval to "never". However, both control panels work on a per-user/login basis and cannot be used to disable yum auto-update system-wide.
    Finally I found /etc/PackageKit/PackageKit.conf, which has a DefaultBackend parameter, but I don't know what I should put there.
    Is there here a way, to disable the yum auto-update system-wide without uninstalling PackageKit?
    I already checked the documentation at http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-PackageKit.html but it was not helpful.
    Thanks!

    The actuall problem I'm trying to fix is the following error:
    <pre>
    Another app is currently holding the yum lock; waiting for it to exit...
    The other application is: PackageKit
    Memory : 45 M RSS (357 MB VSZ)
    Started: Tue Jul 10 09:27:04 2012 - 04:09 ago
    State : Sleeping, pid: 2317
    </pre>
    The above error can happen if you have an active Gnome session and e.g. connect as root using ssh session and try to use yum.
    I may have found a way now to disable the automatic system updates, however, I don't know if this is the proper solution since I cannot find any information about it.
    I modified */etc/PackageKit/PackageKit.conf* and changed:
    <pre>
    DefaultBackend=yum -> DefaultBackend=nobackend
    </pre>
    It requires a re-login of your Gnome X session to take affect.
    Then Administration/Software update does no longer scan for updates, and apparently no longer lock yum at the system level. At least the problem seems to be fixed globally that way.
    I will mark this question as answered, but any ideas are still welcome.
    Thanks!
    Btw, here is a link to previous older thread to disable it on a per-user basis:
    Disable PackageKit Update Applet

  • I want to turn off auto updating on my Mac 10.4.11 How do I do this?

    # Question
    I want to turn off auto updating on my Mac 10.4.11 How do I do this?
    When firefox tries to upgrade (without asking) it tends to upset my Mac's usual functioning.

    You can go into Edit, then Preferences, then Advanced, then update, and set your update settings there.
    Also, FYI, [https://support.mozilla.org/en-US/kb/firefox-no-longer-works-mac-os-x-104-or-powerpc-pr https://support.mozilla.org/en-US/kb/firefox-no-longer-works-mac-os-x-104-or-powerpc-pr]

  • Auto update of events in albums

    Hello! My question is this . . .
    If I create a new album, and then add an event, will the album dynamically update if I add/remove photos to the event?
    Thanks!
    Michael

    Thanks Larry! I think I get it now. Standard albums won't auto update (not dynamic), but if I create a Smart Album ("Travel" for instance), with the event as a criteria (for example, all events that contain the word "vacation"), and if I add photos to any of my "vacation" events, those photos will appear in my "Travel" album. Does this sound right?
    Thanks!
    Michael

  • Air Auto Update Error -- Flash Builder Burrito.

    This is my first attempt at this, so I may be missing something simple.
    I'm not having any luck getting an Air app to automatically update.
    If I manually go to  http://localhost/air1/air1.air and redownload the file I will get a popup that asks if I want to update the app, but when I say ok I get this error.
    "There was an error checking for updates. Error# 16816"
    I haven't found a reason yet,
    Any ideas?
    update.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
      <version>2.0</version>
      <url>http://localhost/air1/air1.air</url>
      <description>1.0 - First version</description>
    </update>
    file -- air1.mxml
    <?xml version="1.0" encoding="utf-8"?>
    <s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
                           xmlns:s="library://ns.adobe.com/flex/spark"
                           xmlns:mx="library://ns.adobe.com/flex/mx"
                           applicationComplete="init()">
        <fx:Declarations>
            <!-- Place non-visual elements (e.g., services, value objects) here -->
        </fx:Declarations>
        <fx:Script>
            <![CDATA[
                import air.update.events.UpdateEvent;
                import air.update.ApplicationUpdaterUI;
                import mx.controls.Alert;
                protected var appUpdater:ApplicationUpdaterUI = new ApplicationUpdaterUI(); // Used for auto-update
                protected function init():void
                    // Check for update
                    this.checkUpdate();
                    Alert.show("checking update");
                // This function is triggered when the application finished loading.
                // Initialize appUpdater and set some properties
                protected function checkUpdate():void
                    // set the URL for the update.xml file
                    appUpdater.updateURL = "http://localhost/air1/update.xml";
                    appUpdater.addEventListener(UpdateEvent.INITIALIZED, onUpdate);
                    appUpdater.addEventListener(ErrorEvent.ERROR, onUpdaterError);
                    // Hide the dialog asking for permission for checking for a new update.
                    // If you want to see it just leave the default value (or set true).
                    appUpdater.isCheckForUpdateVisible = true;
                    appUpdater.initialize();
                // Handler function triggered by the ApplicationUpdater.initialize.
                // The updater was initialized and it is ready to take commands.
                protected function onUpdate(event:UpdateEvent):void
                    // start the process of checking for a new update and to install
                    appUpdater.checkNow();
                // Handler function for error events triggered by the ApplicationUpdater.initialize
                protected function onUpdaterError(event:ErrorEvent):void
                    Alert.show(event.toString());
            ]]>
        </fx:Script>
        <s:Button x="47" y="55" label="Button"/>
        <mx:ColorPicker x="61" y="119"/>
        <s:ComboBox x="77" y="216"/>
        <s:ComboBox x="77" y="185"/>
        <s:ComboBox x="77" y="154"/>
    </s:WindowedApplication>
    file  -- air1-app.xml
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <application xmlns="http://ns.adobe.com/air/application/2.5">
    <!-- Adobe AIR Application Descriptor File Template.
        Specifies parameters for identifying, installing, and launching AIR applications.
        xmlns - The Adobe AIR namespace: http://ns.adobe.com/air/application/2.5
                The last segment of the namespace specifies the version
                of the AIR runtime required for this application to run.
        minimumPatchLevel - The minimum patch level of the AIR runtime required to run
                the application. Optional.
    -->
        <!-- A universally unique application identifier. Must be unique across all AIR applications.
        Using a reverse DNS-style name as the id is recommended. (Eg. com.example.ExampleApplication.) Required. -->
        <id>air1</id>
        <!-- Used as the filename for the application. Required. -->
        <filename>air1</filename>
        <!-- The name that is displayed in the AIR application installer.
        May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <name>air1</name>
        <!-- A string value of the format <0-999>.<0-999>.<0-999> that represents application version which can be used to check for application upgrade.
        Values can also be 1-part or 2-part. It is not necessary to have a 3-part value.
        An updated version of application must have a versionNumber value higher than the previous version. Required for namespace >= 2.5 . -->
        <versionNumber>2.0.0</versionNumber>
        <!-- A string value (such as "v1", "2.5", or "Alpha 1") that represents the version of the application, as it should be shown to users. Optional. -->
        <!-- <versionLabel></versionLabel> -->
        <!-- Description, displayed in the AIR application installer.
        May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <!-- <description></description> -->
        <!-- Copyright information. Optional -->
        <!-- <copyright></copyright> -->
        <!-- Publisher ID. Used if you're updating an application created prior to 1.5.3 -->
        <!-- <publisherID></publisherID> -->
        <!-- Settings for the application's initial window. Required. -->
        <initialWindow>
            <!-- The main SWF or HTML file of the application. Required. -->
            <!-- Note: In Flash Builder, the SWF reference is set automatically. -->
            <content>[This value will be overwritten by Flash Builder in the output app.xml]</content>
            <!-- The title of the main window. Optional. -->
            <!-- <title></title> -->
            <!-- The type of system chrome to use (either "standard" or "none"). Optional. Default standard. -->
            <!-- <systemChrome></systemChrome> -->
            <!-- Whether the window is transparent. Only applicable when systemChrome is none. Optional. Default false. -->
            <!-- <transparent></transparent> -->
            <!-- Whether the window is initially visible. Optional. Default false. -->
            <!-- <visible></visible> -->
            <!-- Whether the user can minimize the window. Optional. Default true. -->
            <!-- <minimizable></minimizable> -->
            <!-- Whether the user can maximize the window. Optional. Default true. -->
            <!-- <maximizable></maximizable> -->
            <!-- Whether the user can resize the window. Optional. Default true. -->
            <!-- <resizable></resizable> -->
            <!-- The window's initial width in pixels. Optional. -->
            <!-- <width></width> -->
            <!-- The window's initial height in pixels. Optional. -->
            <!-- <height></height> -->
            <!-- The window's initial x position. Optional. -->
            <!-- <x></x> -->
            <!-- The window's initial y position. Optional. -->
            <!-- <y></y> -->
            <!-- The window's minimum size, specified as a width/height pair in pixels, such as "400 200". Optional. -->
            <!-- <minSize></minSize> -->
            <!-- The window's initial maximum size, specified as a width/height pair in pixels, such as "1600 1200". Optional. -->
            <!-- <maxSize></maxSize> -->
        <autoOrients>false</autoOrients>
        <fullScreen>false</fullScreen>
        <visible>false</visible>
      </initialWindow>
        <!-- We recommend omitting the supportedProfiles element, -->
        <!-- which in turn permits your application to be deployed to all -->
        <!-- devices supported by AIR. If you wish to restrict deployment -->
        <!-- (i.e., to only mobile devices) then add this element and list -->
        <!-- only the profiles which your application does support. -->
        <!-- <supportedProfiles>desktop extendedDesktop mobileDevice extendedMobileDevice</supportedProfiles> -->
        <!-- The subpath of the standard default installation location to use. Optional. -->
        <!-- <installFolder></installFolder> -->
        <!-- The subpath of the Programs menu to use. (Ignored on operating systems without a Programs menu.) Optional. -->
        <!-- <programMenuFolder></programMenuFolder> -->
        <!-- The icon the system uses for the application. For at least one resolution,
        specify the path to a PNG file included in the AIR package. Optional. -->
        <!-- <icon>
            <image16x16></image16x16>
            <image32x32></image32x32>
            <image36x36></image36x36>
            <image48x48></image48x48>
            <image72x72></image72x72>
            <image128x128></image128x128>
        </icon> -->
        <!-- Whether the application handles the update when a user double-clicks an update version
        of the AIR file (true), or the default AIR application installer handles the update (false).
        Optional. Default false. -->
        <!-- <customUpdateUI></customUpdateUI> -->
        <!-- Whether the application can be launched when the user clicks a link in a web browser.
        Optional. Default false. -->
        <!-- <allowBrowserInvocation></allowBrowserInvocation> -->
        <!-- Listing of file types for which the application can register. Optional. -->
        <!-- <fileTypes> -->
            <!-- Defines one file type. Optional. -->
            <!-- <fileType> -->
                <!-- The name that the system displays for the registered file type. Required. -->
                <!-- <name></name> -->
                <!-- The extension to register. Required. -->
                <!-- <extension></extension> -->
                <!-- The description of the file type. Optional. -->
                <!-- <description></description> -->
                <!-- The MIME content type. -->
                <!-- <contentType></contentType> -->
                <!-- The icon to display for the file type. Optional. -->
                <!-- <icon>
                    <image16x16></image16x16>
                    <image32x32></image32x32>
                    <image48x48></image48x48>
                    <image128x128></image128x128>
                </icon> -->
            <!-- </fileType> -->
        <!-- </fileTypes> -->
        <!-- Specify Android specific tags that get passed to AndroidManifest.xml file. -->
        <!--<android>
            <manifestAdditions>
            <![CDATA[
                <manifest android:installLocation="auto">
                    <uses-permission android:name="android.permission.INTERNET"/>
                    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
                    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
                    <uses-configuration android:reqFiveWayNav="true"/>
                    <supports-screens android:normalScreens="true"/>
                    <uses-feature android:required="true" android:name="android.hardware.touchscreen.multitouch"/>
                    <application android:enabled="true">
                        <activity android:excludeFromRecents="false">
                            <intent-filter>
                                <action android:name="android.intent.action.MAIN"/>
                                <category android:name="android.intent.category.LAUNCHER"/>
                            </intent-filter>
                        </activity>
                    </application>
                </manifest>
            ]]>
            </manifestAdditions>
        </android> -->
        <!-- End of the schema for adding the android specific tags in AndroidManifest.xml file -->
    </application>

    This appears to be a Flex question. Please try posting to the Flex forums here http://forums.adobe.com/community/flex/flex_general_discussion for better response.

  • Apple iOS 7 app auto updates and supervised devices

    I'm in the process of deploying a small number of iPads to our internal users, we had a question around automatic app updates in iOS 7. It would be nice if these devices were able to pull app updates down and install them automatically, but there are 2 problems with this for us. The first is that an itunes account was used to aquire a few free apps, these apps were then installed via configurator, but we will not be signing in to this account on the device. Default behavior unless a supervised iPad is plugged into itunes or signed in manually is to leave the apple id field blank, will updates install without an apple id on the device? Also, if a user signs in to there perosnal apple id will automatic updates download for an app downloaded with a different apple id? Second, were removing the app store from the device, but allowing apps to be installed. This should in theory allow updates to be installed automatically on the device, however we are unsure if this is the case. Does the app store need to be enabled for the device to check in? or does automatic updating happen regardless?

    I can now confirm the apple technician was incorrect. Auto updates WILL NOT install on a device that does not have an apple id signed into it. I've done as much testing as I could with and without signing in and none of the multiple devices I have will automatically download updates until I sign in to the account the app was purchased under. Ultimately this is new for apple, and in addition to that this scenario is faced by very few customers managing these devices So i understand getting this information incorrect. This post is more or less a warning to anyone managing supervised ipads where applications are being installed and no apple id associated with the device, dont rely on automatic updates to keep your apps up to date; you will either have to sign into the ipad and turn on automatic updating, or manually install each update via configurator when they are released.

  • HP Auto Update

    My HDMI video and audio were fine. However, after HP Auto Update prompted me to update with out any cancel button, and it automatic updated by itself, there was no sound from my TV, and also, the display was bigger than my TV. After that I did a system restore, and my HDMI video and audio are working fine again.
    My question is:
    How do I stop HP Auto Update from updating automatically?
    Please advise.

    Hi @bktran 
    Welcome to the HP Forums!
    It is a terrific place to find answers and information!
    For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
    I understand that an HP update was installed and you lost the audio and the resolution on the display had been changed.
    You did a restore and everything is back to normal.  You would like to know how to stop the update from being installed.
    Here is a link to Change how Windows installs or notifies you about updates  that will allow you to choose by changing the setting.
    Best of Luck!
    Sparkles1
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

  • How to disable software auto update from iPad

    I was trying to download my favorite programs and iOS 7, but first I have to stop software auto update, how will I do this?

    The actuall problem I'm trying to fix is the following error:
    <pre>
    Another app is currently holding the yum lock; waiting for it to exit...
    The other application is: PackageKit
    Memory : 45 M RSS (357 MB VSZ)
    Started: Tue Jul 10 09:27:04 2012 - 04:09 ago
    State : Sleeping, pid: 2317
    </pre>
    The above error can happen if you have an active Gnome session and e.g. connect as root using ssh session and try to use yum.
    I may have found a way now to disable the automatic system updates, however, I don't know if this is the proper solution since I cannot find any information about it.
    I modified */etc/PackageKit/PackageKit.conf* and changed:
    <pre>
    DefaultBackend=yum -> DefaultBackend=nobackend
    </pre>
    It requires a re-login of your Gnome X session to take affect.
    Then Administration/Software update does no longer scan for updates, and apparently no longer lock yum at the system level. At least the problem seems to be fixed globally that way.
    I will mark this question as answered, but any ideas are still welcome.
    Thanks!
    Btw, here is a link to previous older thread to disable it on a per-user basis:
    Disable PackageKit Update Applet

Maybe you are looking for