Issue 117148 - wizards: Guidance of "Deactivating the Registration Wizard" does not fit
Summary: wizards: Guidance of "Deactivating the Registration Wizard" do...
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 3.3
Hardware: PC Windows XP
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: needhelp
Depends on:
Reported: 2011-03-01 13:41 UTC by salvator
Modified: 2014-03-04 12:41 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description salvator 2011-03-01 13:41:24 UTC

we install by using a network installation file, not by single installation per client.
To have a uniform start configuration, we want to deactivate the „registration wizard“. Up to Version 3.2 this feature worked quiet well, but now our activities do not work anymore.
We used the informations from Wiki „Deactivating the Registration Wizard“ by editing the „common.xcu“ , „settings.xcu“ and „setup.xcu“.

The only things we changed was in „common.xcu“ the part <value>Patch9567</value> to have the correct patchpack- number and in „setup.xcu“ the „LicenseAcceptDate“ to <value>2011-12-30T08:14:11</value>. Even by complete new installations, we get the startmonitor with registration infos and when we do change nothing, it works as well not. That is not wanted, because most normal users will accept this and than activate a online process, we do not want them to have and that causes supporttrouble.

Does somebody know, how we can act, to use the deactivation of the „Registration Wizard“ in 3.3? What must happen too, to deactivate them ( except „common.xcu“ , „settings.xcu“ and „setup.xcu“)? Is there any new tool to manage the startconfiguration? Thank you for your help.
Comment 1 Olaf Felka 2011-03-01 14:05:48 UTC
Please have a look
Comment 2 thorsten.martens 2011-03-01 14:41:51 UTC
tm -> salvator: Please have a look at issue 117013. Maybe that issue describes the same problem and therefore this issue might be a duplicate. If it is not the same problem, please provide more information like the network installation file which is used and a clear description of which entry in which file has changed from which value to a new value.
Comment 3 salvator 2011-03-04 12:47:16 UTC
I don´t understand the Issue 117148. So I can´t decide, whether it is the same bug or not. 

===what I can see in Issue 117148====
  Description From   2011-02-18 13:12:01   (-) [reply]

Due to a side-effect in the startup and deployment code an extension installed
in the shared layer is not able to disable the first start wizard for the first

------- Comment #1 From 2011-02-18 13:13:57 (-) [reply] -------

cd: Set kso on CC. Accepted issue.

------- Comment #2 From 2011-02-25 11:13:14 (-) [reply] -------

cd: Fixed. The fix moves the code which evaluates the restart flag up. We can
now check it before calling the first start wizard. If we want to restart it
makes no sense to show the first start wizard.

cd->mav: We already did a code review. Please approve my changes.

------- Comment #3 From 2011-02-28 09:41:45 (-) [reply] -------

The fix is reviewed and looks good.


Where can I find the fix to test it and what does this fix do?

My purpose is, to stop the individual menues to configure, because many users are too confused by managing these steps before starting the first time ( after release or first time installation). 
OK, if it is not managing, we have the opportunity to make a startconfiguration and copy this to the userprofile in the Folder, but the "old" way is more comfortable. Thank you for inspiration.
Comment 4 Oliver-Rainer Wittmann 2012-06-13 12:30:51 UTC
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.