Has anyone else tried creating a local WPS 8.0 Installer for Windows 7?
Just curious to know if any other long-time WPS admins out there have tried creating a local WPS 8.0 Installer that works on Windows 7, and if you had any luck?
Wise/Altiris (pre-Symantec) officially dropped support for local Wise installs after v5.x, but... as many of us know, it was still possible to keep doing this via a script that installs MSDE, then Wise 6/7/8, then manually selecting "(local)" for all database values. The local install option was tremendously helpful for companies with packagers that work offsite or from home (slow or no connection to company packaging server), or that use contractors/vendors to package. It was also very useful as a 'plan B' option in the event something bad happened to your packaging server.
Why Altiris/Symantec ever decided to drop support for this is beyond me, and in my opinion, another good reason why so many of their customers are bolting to AdminStudio and other products. But that's a topic for another discussion...
Back on topic: I spent a goodly portion of this month developing and testing a new Win7 compatible local Wise 8 install script based on SQL Express 2008 R2. It works, but is ridiculously slow (20-40 mins). The main problem is the database configuration part: WiseAdmin.exe. I'm seeing up to 30 minutes of needless delays in the Event log due to the SQL Server service (MSSQLSERVER) repeatedly trying to auto-start the (local) Workbench, Software Manager and Wise Services databases, then finally timing out. After they do time out, you get to the WiseAdmin.exe 'finish' dialog and... magically somehow everything works fine after that point. If I could eliminate the 20-30 minutes of needless service startup delays, I could chop this thing down to ~10 mins and everyone would be a lot happier.
Any ideas from the Wise gurus out there?
Thanks,
Comments
My guess is that the
My guess is that the configuration of the SQL Server Express install is not optimised for WPS. I have used both SQL Express 2005 and 2008 with WPS 7 and the install process has no delays when performed manually following the instructions provided in the old Altiris KB.
The KB information is now in the new Symwise KB, so if you go here:
http://www.symantec.com/business/support/index?page=answers&startover=y&question_box=SQL+Server+Express&product_finder=Wise+Package+Studio&productselectorkey=56161&myclicker.x=7&myclicker.y=8
you will find links to a number of articles about setting up SQL Server Express for use with WPS.
I have not tried with SQL Express 2008 R2 but I would expect the same basic settings to work with this version as it has for the previous versions.
Let us know how you get on.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Thanks, Ed,
Thanks, for the links to those KBs, Ed. Unfortunately, it didn't make any difference.
At first I was excited when I read that PDF "Installing SQL Express 2008 for use with Wise 8". But... following Symantec's advice and appending "\SQLEXPRESS" (or whatever SQL instance name you used) to "(local)" actually generated an "unable to logon to database" error. Going back to just "(local)" allowed me to complete the WiseAdmin wizard, but with the same slowness.
However, this time I did notice something else: the slowness issue is worse on 32-bit Win7 than 64-bit Win7.
Have you tried manual
Have you tried manual installs to see if there are any issues arising?
Are you using the 64 bit edition of SQL Express 2008 R2? I have only ever worked with 32 bit editions so cannot comment whether there are any issues with using the 64 bit version.
I do recall that installing on Vista required UAC to be turned off, but this was back with WPS 6. It would be interesting to test the Win 7 install with UAC turned off also, since elevation is certainly needed to get both the SQL Express software installed, and also the WPS software. However, using the "Install as Admin" right click option on the installation executables, runs the install in the context of the local admin account and not in the context of the current user, so I wonder if there could be any user profile issues, as WPS's licensing information is stored in HKCU and is only valid for the installing user. Therefore the installation has to be carried out using the credentials of the user account that will subsequently use the tool, and elevation has to be applied to that account to permit correct installation. By turning off UAC, you at least enable your admin account to run with full admin privileges so no additional elevation is required during the install.
If you can get it all working manually, then at least you are on the way to getting it all working via an unattended install, which I believe is your aim. I cannot recall whether the SQL server express install requires a reboot to get all the services running, but a manual install will show up any such requirements.
One final thought - if you continue to have issues with SQL Express 2008 R2, try the R1 version.
By the way, if your intention is to create packages for multiple environments, eg XP and Win 7, then standard practices recommend you package on XP rather than Win 7, as this creates less issues with the resultant packages. You may also find that turning off UAC makes life easier when performing tasks such as capturing old applications. This leads me to another point - the WPS 8 capture engine does not work fully on 64 bit operating systems, so if you have a requirement to capture applications, do not use a 64 bit operating system as your test platform. (Capture is a 32 bit process so only records changes to the 32 bit areas of a 64 bit operating system)
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
You made some good points,
You made some good points, Ed.
Re: SQL Express 2008 R2 - I match the version of SQL Express to the OS --in other words, I install 32-bit SQLE on Win7 32-bit and the 64-bit version on Win7 64-bit.
Re: UAC - we have also run into issues with this before, so a pre-requirement of running a local Wise install is to turn off UAC (set to lowest possible setting).
Re: reboot - I have not yet seen any reboot prompts on a manual install of SQLE 2008 R2 & Win8.0.
Re: SQL Express 2008 R1 - that's not a bad idea. I'll have to try that and see if I get better results.
Re: Wise SetupCapture on Win7 64-bit - I couldn't agree more. When Symantec says Wise 8.0 is "compliant" on 64-bit Windows 7, "compliant" is mighty loose term ;-). For starters, the default exclusion list doesn't have *any* Win7 entries, much less 64-bit. Wise Web Capture and other tools either don't work at all or work poorly on 64-bit.
Just for the record. There is
Just for the record. There is no such thing as SQL Express 2008 R1. Only SQL Server Express 2008 including SP1 and SP2 (so far). R2 is different, because it contains some new features.
The naming scheme by Microsoft is not the best in my opinion, because people will mix this up with Windows Server 2008 R2, which is a 64-bit operating system only.
Sorry, my mistake. I was in
Sorry, my mistake. I was in fact referring to SQL Express 2008 with whatever service packs are applicable currently. I wrongly assumed that this was actually called the R1 release to differentiate it from the newer R2 release, but this would appear to be incorrect.
You make a valid point with your reference to 64 bit operating systems. As I understand it, there is a difference in the way that 32 bit and 64 bit DSNs are created, but I am unsure whether a 64 bit version of SQL Express can be accessed with a 32 bit DSN. Since the Wise products are all strictly 32 bit applications, and the tech notes have always referenced 32 bit versions of SQL Express, I would personally stick with what has worked for me in the past, even on a 64 bit O/S.
At some point, I am going to have to bite the bullet and set up a 64 bit VM on my 64 bit laptop and do some experimenting with the different versions of SQL Express, but in the meantime, if you get to any conclusive point, please let us share your experiences.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Would you like to reply?
Login or Register to post your comment.