On my domain server 2012r2I am trying to deploying office 2007 but not all of the office I need to install only excel and word
I found an .msi file within the dvd installation and found many .msi packages
called ExcelMUI.msiand WordMUI.msi at directory
...\English\Excel.en-us\ExcelMUI.msi
...\English\Excel.en-us\WordMUI.msi
can I use them to deploy only excel and word through domain server 2012r2?
are they valid as .msi packages installer ?
Best Guess: I wonder if those MUI-setups are Multilingual User Interface setups. I think you should get on a virtual machine and try to run the setup.exe instead (if there is one) and then go to "Custom" or equivalent to see if you get a feature selection dialog. Then you should select Word and Excel to install fully and you can disable most other features (don't disable the shared features, just the other apps would be my suggestion - Outlook, PowerPoint, etc...). It is possible that those MSI files you mention can be used directly. You could try to run them - but only on a virtual of course. Or on a computer which does not matter - test computer of some sort. Look for a custom option and a feature dialog there too. Sorry, all I can suggest without installation media access.
Sure?: With all that said, Office on a domain server? Do you mean domain controller? (hope not). Sounds like a very dangerous move if you ask me - with all the security holes Office contains. At least make sure to run Windows Update or Office Update or whatever mechanism you have to deploy security fixes. Can I be curious and ask why the server needs Office? Is it for automation only?
Viewer for MSI Files: You can open and inspect MSI files using the free tools Orca, SuperOrca or InstEd (links towards bottom). I have an old answer on superuser showing how MSI features can be seen inside the MSI file.
Related
I am attempting to use a Packaged Solution for my Access 2010 application that has its backend linked to SQL Server. At the moment, I'm using the .accdb file as the frontend, and I would like to distribute my application to some other Windows computers, but the Packaged Solution does not work. I had the package include Access Runtime, so their version of the frontend is running on Runtime and not full Access. However, once the application makes a request to the backend, the application does nothing, as I am not even prompted for the SQL Password as per usual with the full version. I've read on about including a .dsn file in the package can secure the SQL connection (see here), but going through steps of other tutorials to create .dsn files hasn't led to any results. Would anyone know how to correctly generate the .dsn file or if I've done something else wrong at this point?
(And yes, I understanding using Access 2010 in the year 2019 is almost a joke at this point, but I'm doing this for testing purposes. I plan to completely remake the frontend in Angular in the future.)
One other unrelated note... would it be a better idea to have the frontend hosted as a .html file like through the "Publish to Access Services" process? I did read that Access Services was discontinued last year, so would that not be possible?
Edit: This is not a duplicate of "DSN Less Connection (MS Access to SQL2016)" because A) I want to utilize a DSN Connection, not DSN-less and B) I am not using connection strings in my code to hook up with SQL.
You should be able to just create FILE dsn, link your tables, and then distribute the compiled accDE to each desktop.
However, what SQL odbc source provider did you use? If you use the SQL server ODBC provider, then that is by default installed on each computer.
However, if you linked using Native 11 (or later), then that driver is NOT installed on each workstation by default. So, I HIGH recommend you create a FILE dsn (not a user or system DSN), and link the table using that. (Access will create DSN-less links for you)
And you should NOT be seeing a logon prompt with your application. This suggests you forgot or missed the save password option.
So, I would re-link your tables, creating a new FILE DSN. And if you using the linked table manager, then make sure you check the prompt for new location to force creating of a NEW DSN. If you just re-fresh, then you DO NOT get a chance to click on the save password option during the linking process.
So, what odbc driver are you using? The native 11 or later are better, but they are not installed by default on each workstation. However, CAUTION is required here, since the older sql driver does NOT support the newer datetime2 formats. If you used these newer sql column types, they will be returned as string data types in Access and create a mess of issues.
So, first, I would re-link using a FILE dsn.
Make sure you check the save password during the re-link.
You then compile your accDB into an accDE, and then distribute that. You don’t really need to use the package wizard, since once each workstation has the runtime installed, then a simple copy of the accDE to each person’s computer will thus work fine. There is NO special connection between your accDE and the package wizard. Once the runtime is installed, then any and all mdb, accDB, and your accDE can simply be clicked on to launch + run. So for testing, you can skip the package wizard, and just copy the accDE to the target machine, click on it, and see if it works.
Edit
The prompt and check box during this process is this:
So you have to check that box to save the password. Note that you ONLY get this dialog WHEN you create a new FILE dsn.
I've had a look at the chef community cookbook for installing sql server and it appears that it's tailored for installing SQL express, but I can't seem to work out how to install a standard or developer edition.
The README on the GitHub page (https://github.com/chef-cookbooks/sql_server) says you can just point it to any installation package, however I can't see how you would do this for an ISO (or even the extracted contents of an ISO) given that there's no single EXE package on the ISO media.
Am I missing something obvious, or will I need to roll my own recipe for installing SQL from an ISO (or contents of ISO)? Ideally I would like to host the installation media on a central package repository behind my firewall.
Option 1:
Customized cookbook is the best option for you use case. Like you said, host .ISO on central repo and create a cookbook that mounts the .ISO drive to run the installation. You should leverage that cookbook template and re-write that windows_package block in the server.rb to install using keyword 'source' with path to the mounted installation files. However, this will be a major work (from past experience...) so if you have only one or two nodes that need to run the cookbook, go with Option 2.
Option 2:
If you have only one or two nodes that need to run the cookbook, I would suggest you to run the basic 'sql_server::server' then upgrade to the version you want using the GUI with the PID product key.
Note that this process can be automated as well using Powershell script. If you are familiar with Powershell, you can automate it using powershell_script block.
ISOs are intended for DVD images but if you have an ISO shredder (search online for free tools) you'll see a setup.exe in there. Run that and it'll bring you to the installation center where you can choose to install a new instance and do a bunch of other things. It's a wizard type interface so just read the instructions on each page and you should be able to provide the relevant info where needed to successfully complete the installation
Suppose I have a dialog box for giving an instance name and I want to see what are the other instances available in the local machine or the server and what if the user has both SQL Server 2005 and SQL Server 2008 installed in his system and I want to choose the instance name to deploy the database into. How do I achieve this using a Setup project created using Visual Studio 2010?
Please guide me as I'm new to Setup project.
Thanks
The problems are that VS setups don't let you build your own customized dialogs to show at the start, and don't let you run code to populate them or validate the contents. That means you're not really using the setup project because you'll end up writing your own code to do all this. Although you might be tempted to run this code as custom action, it will run with the system account (in an Everyone install) and the dialogs won't work properly because you'll not be running in a Windowing STA context. So you could integrate all this into the setup if you used another tool (such as WiX) and designed your own dialog to show during the standard install dialogs. The general design pattern is that you collect the info and stoer it into properties that are used with cusom actions in the execute sequence to make the changes. This happens to enabled silent install, specifying the property values on the msiexec command line or group policy delivery.
With VS you'd be better off having the user run your code to configure all this after the install at first run of the app.
Just provisioned a new server running IIS and Server 2012 and SQL Server 2012. I also installed SQL Server Management Studio tool so I can quickly inspect databases without the need to open a remote connection.
When I browse an ASP.NET sites remotely, I get a Just-in-time debgugger exception dialog when an error is encountered in addition to the yellow screen. The dialog stays up on the server and piles up unless I RDP and manually close all the dialog boxes.
The only way to disable this is by removing Visual Studio Shell 2010 (integrated) using the control panel. The side effect is that I can no longer use SSMS.
Most of the available solutions are outdated or don't work. The registry settings are no longer applicable and most articles concerning this issue are old. Microsoft's official documentation is a rat's nest of broken links. Moreover, many users are confusing IE's script debugging dialog with this issue. Although they are related and similar, this specific issue is tied to Visual Studio's runtime environment.
Any ideas?
ASIDE: I can't believe Microsoft has this "feature" on a product that is installed on a production server. I am just floored by the incompetence of a multi-billion dollar corporation. I've seen my question asked since at least since 2005 with no official solution that works. I just have to ask one last time for sanity checking. I want to make sure I'm not the one who is "thick" in the head here.
To disable Just-In-Time debugging by editing the registry
In the Start menu, click Run.
In the Run dialog box, type regedit, then click OK.
In the Registry Editor window, locate and delete the follow registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger
If your computer is running a 64-bit operating system, delete the following registry keys also:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\WindowsNT\CurrentVersion\AeDebug\Debugger
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\DbgManagedDebugger
Take care not to accidentally delete or change any other registry keys.
Instead of deleting it, you can also just (temporarily) rename the AeDebug key for the bitness of your choice to something else, e.g. AeDebug-disable!
For server 2012, IIS, and SSMS 2014 we tried all three registry three deletions and those did not work.
What did work was old school renaming the JIT Debug executable.
Renamed these files.
C:\WINDOWS\system32\vsjitdebugger.exe
C:\Windows\SysWOW64\vsjitdebugger.exe
Renamed this folder
C:\Program Files\Common Files\Microsoft Shared\VS7Debug
As a follow-up to nfox's answer, I've created a registry file that you can simple use instead of searching manually through regedit.exe.
1.) Copy this script to your clipboard:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug]
"Debugger"=-
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework]
"DbgManagedDebugger"=-
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug]
"Debugger"=-
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework]
"DbgManagedDebugger"=-
2.) Save it to a file with the .reg extension:
E.g. to a file named
C:\Users\<user name>\Desktop\DisableJit.reg
3.) Double click the file
After confirming the appearing message box, the keys are getting deleted.
5.) Alternatively: Download file
If this is too much effort, you can download the registry file from here:
disable-the-just-in-time-debugger-windows-64-bit.reg
disable-the-just-in-time-debugger-windows-64-bit.zip (As a ZIP)
Download and then double-click it.
This tip was simply taken from the MSDN article "Just-In-Time Debugging in Visual Studio".
The syntax on how to delete registry keys via a .reg file was taken from the MSDN KB article "How to add, modify, or delete registry subkeys and values by using a .reg file".
You should be able to disable Jist-In-Time debugging using the Debug options dialog inside Visual Studio. The registry keys are also well documented here.
See:
http://msdn.microsoft.com/en-us/library/5hs4b7a6.aspx
Aside: I think it's not a wise thing to install a management studio on a production server. This is what management workstations are for. Remote connections from a management station can be pre-configured and stored so that it doesn't take much effort. That way you can keep your production environment clean.
I download jdeveloper studio edition and install it in C:\Oracle\Middleware
then I install weblogic instance using C:\Oracle\Middleware\wlserver_10.3\common\bin\config.exe
to C:\myproject\domains\myweblogic
Then download DMS_11.1.0.0.0_WINDOWS.zip and install it to C:\Oracle\Middleware\Mobile.
thereafter cant start
C:\Oracle\Middleware\Mobile\Mobile\Server\bin\runmobileserver.bat
unless i change the variable to this batch file
set DOMAIN_DIR=C:\myproject\domains\myweblogic
what do I do next to see that it works?
is there a simple example that creates a sigle table and synchronized between server and mobile clients?
very difficult to find information on this technology. interfere very popular tags (Oracle, Database).
If you install Database Mobile Server directly in the WebLogic directory, you will not need to edit the batch file. For instance, I believe the default install directory is:
C:\Oracle\Middleware\wlserver_10.3
So if you used the default install directory, you would install Database Mobile Server there, with no added 'Mobile' or other directory. If you chose to install WebLogic elsewhere, then replace the above with that directory.
There is another small issue to be aware of.
The installer will give you warning about installing in a non-empty
directory. You should click through the warning. This is a known issue
documented in the Release Notes.
Regarding your other question about a demo, there is a Java demo found in
<MOBILE_HOME>\Mobile\Server\demos\consolidator_api
You will need to download a client and perform a sync, which is documented here:
http://download.oracle.com/docs/cd/E22663_01/doc.11100/e22681/instsqlite.htm#BABGAACI
I hope that helps, good luck with your project. Let me know if you have further questions.
Eric Jensen, Oracle PM