PowerShell must be installed for the script to work. This program is bundled with all modern windows systems, but in WindowsXP you have to install PowerShell separately.
All parameters of the script can be set by editing the file, or can be passed as the values of the corresponding keys. Let's take a look at what keys are and what values they need to pass.
Key "dd" (from Distribution Directory), accepts any path in windows format, i.e. paths like "C: \ Windows" or "\\ Server \ 1CDistr". The specified path must contain distributions of the 1C platform, and each of the distributions must be in its own folder with the version number or version number and the bitness of the 1C Enterprise platform, for example, "8.3.5.1111" or "8.3.9.1818-32" or "8.3.9.1818 -64 ". The bitness suffixes must be used if there are computers with operating systems of different bitness on the same network and you want to install a 64-bit platform on a 64-bit system. The specified folder, and all subfolders with platform distributions, must be readable by the user on whose behalf the script will run.
The "dl" key (from Directory Logs), similar to the "dd" key, accepts any path in the windows format. The script execution logs will be written to this folder. The names of the log files correspond to the computer name and are added each time the script is run. The specified folder must be writable by the user on whose behalf the script will run. If the specified path is not available or there is no recording capability, then all script actions will be written to the file "1C8InstallAndUninstall.log" located in the user's local folder (approximate path "C: \ Users \ Vasa \ AppData \ Local \").
The "ip" key (from Install Parameters) is responsible for the installation parameters when the script is running. The key can take one of the following values:
- “No” - do not install
- “Last” - install the latest platform found in the distribution folder
- "8.3.5.1111" - the version number of the specific platform that you need to install
The "dp" key (from Delet Parameters) is responsible for the deletion parameters when the script is running. The key can take one of the following values:
- “No” - do not delete
- “Ael” (from all except last) - delete all platforms found on the computer that match all platforms found in the distribution folder, except for the latest platform. Important! This key will remove only those platforms, versions of which are available in the folder with platform distributions, if some version is installed on the computer, but it is not in the folder with distributions, then it will not be deleted.
- "8.3.5.1111" - the version number of a specific platform that needs to be removed
- “All” - remove all versions of the 1C platform on the computer. This meaning is overwhelming and extensive. Overwhelming, because for the script to work with this value, it is necessary to pass the path for writing logs, or you can not even pass it, all the values of the other keys will be ignored. Extensive, because all products on the computer will be removed, even if they ghostly resemble the 1C platform.
The "iod" key (from Installation Options Distribution) is responsible for the components of the 1C platform that will be installed. The key must be passed a value of the form "DESIGNERALLCLIENTS = 1 THINCLIENT = 1 THINCLIENTFILE = 1", in which you can change 1 to 0 or vice versa, depending on which parts of the platform you want to install. If this key is passed any other value that is not similar to the line above, then all components will be installed for the system to work in client mode.
- "DESIGNERALLCLIENTS" - main client and configurator
- "THINCLIENT" - thin client for client-server operation
- "THINCLIENTFILE" - thin client with the ability to work with file infobases
How to install, update or uninstall the 1C Platform, if you have a lot of computers, to run to everyone, but there is no domain?
Bad news: you have to run around and configure the execution of the task scheduler on each computer
The good news is that you only need to do this once.
First, let's carry out the preparation:
- Create 2 public folders, one with read access for everyone and the other with write access for everyone. Be sure to create 2 independent folders, otherwise everything can end very badly.
- We put folders with distributions in a folder with "read-only for all" rights, each of the folders should be named according to the version number of the distribution kit that is in it. Here we put the script and the bat file that runs the script.
A small digression! Why do we need a bat file to run a PowerShell script? Because using the bat file we kill two birds with one stone:
- By default, the windows system prohibits the launch of any PowerShell script for security reasons, so the bat file will first allow the script to run, and then prohibit it again after it is running.
- In the bat file, you can change the script launch parameters without editing the script file itself, changing the default values set in it.
Now let's start configuring the user's local computers. In the absence of a domain, it is assumed that all users work under local accounts with "Users" rights, and for administrative actions there is an account with "Administrators" rights.
How to install, update or uninstall 1C Platform if you have a domain?
Everything is nowhere easier
Note
- The script has been tested on the following systems: Windows 7 (x86, x64), Windows 8.1 (x86, x64), Windows 10 (x86, x64) with all mandatory and optional updates for 2016-11-10.
- If you are not satisfied with the delay in the execution of the script in the domain, then you need to set the parameter "Configure Logon Script Delay" to "0". The setting can be found: Computer Configuration> Administrative Templates> System> Group Policy> Configure Logon Script Delay. Thank you very much for this information.
upd: 2015-12-07
- The way of traversing directories with the platform has been completely rewritten. This part of the code had the most complaints, not all of them worked out this part, and for some it worked out incorrectly. Now everything works as expected. only the simplest constructs are used to traverse the distribution directory.
- The part of the search for the latest (older) distribution kit in the distribution kit folders has been completely rewritten. Now this is normal understandable code, and not the horror that was before.
- Parts of the code have changed among themselves, now the script tries to put the platform first, and then everything else.
- Many different checks have been added to avoid strange behavior or unnecessary attempts to install the platform. The log file now contains more information about the operation of the script.
upd: 2016-11-21
- The logic of the script has been changed. Now the platform installation is checked, and if the installed platform is absent on the client computer, the script stops working.
- The functionality has been added that allows installing a 64-bit platform on 64-bit systems in a network with computers of different bitness. For this functionality to work, the folders with platforms must be of the form "Х.Х.Х.Х-32" and "Х.Х.Х.Х-64".
To completely remove any version of the 1C Enterprise program from your computer, I advise you to first delete the information database. However, if you know exactly where the database is located, the order does not matter.
Removing the information database 1C Enterprise
I'll make a reservation right away that this article deals with the removal of only the file version of the database. If the database is server-based, you need to contact the server administrator.
To determine where the database is located, you need to run the 1C program. After starting, the following window will appear with a list of your infobases:
At the bottom is the path to the database directory (I have highlighted the line with a red rectangle). It is this directory that needs to be removed from the hard disk (only the last directory in this path, in my example it is "Temp", which is located in the "Base 1C" directory).
Get 267 1C video tutorials for free:
Open "Explorer" and look for the directory we need:
Click on it with the right mouse button and select "Delete".
We do the same with other information bases.
If the database is located on another computer (the path will look something like this: "File = \\ ALEXPC \ 1C Databases \ Temp"), it is better to go to that computer and delete it there. If knowledge allows, you can try to delete it from this computer.
Removing the 1C Enterprise platform
The 1C: Enterprise platform is removed in the same way as a regular program, through the Control Panel.
We go to the "Control Panel". Depending on the version of Windows, the panel can be found by clicking either the right or left mouse button on the "Start" button. On Windows 10, right-click:
Executing wix package from package will output "error 1316: account specified already exists" during upgrade. How will Windows Setup display this error code? I'm afraid there is no documentation on this.
We previously released a product consisting of a single msi package and now we are preparing an update consisting of a wix package containing a new version of this msi package. The product ID and file name have not changed between the original msi package and the update.
Change: the msi package does not yet support the upgrade. When a user needs to update (when it will be a major update, a minor update, or a minor update), he must first manually uninstall the previous package ...
Edit 2: I just removed the references to use the extension to compile and the installer seems to work fine ... I still need to fully test it.
4 answers
An MSI upgrade requires the MSI to have a new ProductCode, a ProductVersion increment (in the first three fields), and the same UpgradeCode. So it's not clear to me that you are actually getting the update, depending on what thinks you are drinking. It cannot update because you have the same ProductCode. (A MajorUpgrade element in the MSI is required to perform the corresponding upgrade). Therefore, there is some doubt as to whether you are getting the actual full update. If you intend to replace the installed MSI with a full update and a higher versioned product, use the MajorUpgrade function.
So Burn may decide to do an in-place update by reinstalling the MSI file (and this is more like a patch than an update) and this is relevant because you don't say if you have any custom actions or features of using WiX (they are still are custom actions) that create a user account. If you do, then the most likely reason for your error is that Burn reinstalled the new MSI as an update by reinstalling the MSI file and some custom actions just started running again and yes, this user still exists because there was no actual uninstall which will remove it. Or the ProductVersion of your MSI is the same and you have a maintenance mode repair, so the custom action will run again.
I would get a detailed update log to see exactly what is going on.
There's a lot of guesswork out there because you say you want updates, but your MSI is not built to actually update, and you don't say if you have WiX that uses a user to create a user account. You also don't say if you have increased the ProductVersion of your new MSI, so again this leads to additional guesses as to what Burn might do. The verbose log will indicate if this is a user action issue or something else, what update (if any) you are doing.
I had the same problem and since win10 won't let me run the fixit from the internet, I did the following hack to remove the Asus Smart Gesture on my Windows 10 laptop.
1. You need to spoof MS site thinking that your computer is not Win10. I installed a Chrome add-on that allowed me to change the chrome browser user agent to think I am IE9 and a previous version of Windows: Mozilla / 5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident / 5.0)
2. This allows you to see the fixit button and download the portable version of the tool (in case you need to use it for non-network clients)
3. Download and extract to my download library in a folder named fixitp.
4.If I run the exe directly, I get some nasty script error. What I did to work around this was to go to the Resources folder and then to the Troubleshoot folder.
5. I ran Program_Install_and_Uninstall.diagcab, which launched and allowed me to successfully uninstall the Asus SmartGesture program.
6. Then I installed the new version of ASUS Smart Gesture from my website.
I suspect that any installed application that you cannot uninstall may be resolved by the same process - just not running in any other that is included.
. Yesterday, at last, with the help of the installer, I updated my eight to the newfangled ten on all machines. However, I ran into one significant problem.
The fact is that the Classic Shell program, which returns a more convenient view of the "Start" menu, suddenly refused to work, when trying to reinstall it, the error "the specified account already exists" began to appear. The same message appeared when trying to delete it.
After lengthy dances with a tambourine, about the same as in the case of the error, I suddenly found a simple solution.
Solution
So, if your channel allows you to watch a video, then you can follow me step by step to eliminate the problem “the specified account already exists”.
If you have a rather weak Internet, then here's what you need to do:
- We delete the folder with the installed program, for this we go to C: \ Program Files if our ill-fated program is not there, then we scratch in C: \ Program Files (X86).
- We open it, go to the section Important registry keys, at the top, enter the name of the program in the search box, then go through all the tabs, and if any entries appear, delete them.
Attention!!! Do not delete unnecessary things, only that which is related to the program.
- We go to the section "Cleaning the registry" and search for problems, which are then eliminated in automatic mode.
We rejoice at the running installer or the remote program. The error "the specified account already exists" will not bother you.
Subscribe to my YouTube channel! Many more useful videos are waiting for you!
