Server Management Suite

Installation (64 bit)

Attached is a use case for the Installation of the ITMS 7.1 Beta product. Please log your installation issues here in this forum. The forum will be monitored by both QA and others to watch for issues that arise.

Attachment(s)

Beta Use Case 7.1 Installation.zip   64 KB 1 version

Hi

I get an error saying

Installation of SIM cannot proceed. The following requirement(s) were not met:

Microsoft Windows Server 2003 or latest Server edition of Windows is required.

when I fire up the SIM Installer. This seems REALLY odd given that I'm running Windows 2008 R2 Standard. What is the problem here? What can I do to get past this check so I can actually install the SIM?

Regards,

Hi There,

On the Install Readiness Check page, I am getting a message saying the following requirements need to be met before continuing installation

ASP.NET

IIS script maps must be properly configured for ASP.NET

I have clicked the "automatic fix" button a couple of times, but the message still appears.

Removing the AD Services Role "fixed" the problem. Can a SMP 7.1 not be a AD server?!?!?

Regards,

I used advise elsewhere on the forum to skip the AIM checks, so my install is now progressing, but I have hit another error.

Not sure if it is related to the AIM error or a different issue, any advice?

Hi,

I havent had the time yet, but anyone installed successfully yet?

SMP server Windows 2008 R2 standard no servicepack

offbox SQL server 2008 SP1

Installed without any errors, very nice prereq check way better than 7.0

Cheers

So far so good, had a few issues I needed to deal with regarding 2008 SQL R2, but I have to VM's running ITMS 7.1 right now.

I am still trying.  The database permissions were wrong during the install so it failed during the configure.  I got the DB perms sorted out and am trying to reconfigure CMS and it fails when trying to configure Unix, Linux, and Mac something or other.  The error is below.  I tried to copy and paste from log viewer but it doesn't get the whole error no matter what I do so I had to get this from the actual log file. 

<event date="Oct 14 15:51:51 +00:00" severity="2" hostName="ALTIRIS-NS71" source="NSMessageQueue" module="AeXSVC.exe" process="AeXSvc" pid="1432" thread="12" tickCount="3126343"><![CDATA[Failed to receive NS message (GUID: '3b4e4f1f-0cc4-4548-a463-53584f457958' Class: 'f03722b6-5f0e-4034-a2e1-9b2d1ea7422a'):
Altiris.NS.Exceptions.DatabaseNotReadyException: Failed to construct DatabaseContext object. Connection to database failed.
   at Altiris.NS.ContextManagement.AdminDatabaseContext.ThrowDatabaseNotReadyException(String exceptionDetails, Exception innerException)
   at Altiris.Database.DatabaseContext`1.Initialize(Boolean beginTransaction, IsolationLevel isolationLevel)
   at Altiris.Database.DatabaseContext`1.GetContext(Boolean createNewTransaction, IsolationLevel isolationLevel, Boolean independentContext)
   at Altiris.Database.DatabaseContext`1.GetContext(Boolean createNewTransaction, IsolationLevel isolationLevel)
   at Altiris.Database.DatabaseContext`1.GetContext(Boolean createNewTransaction)
   at Altiris.Database.DatabaseContext`1.GetContext()
   at Altiris.NS.ContextManagement.DatabaseContext.GetContext()
   at Altiris.NS.Messaging.NSMessageQueue.TransportableMessage.GetMessageType(Guid messageClassGuid)
   at Altiris.NS.Messaging.NSMessageQueue.TransportableMessage.ConvertToMessage()
   at Altiris.NS.Messaging.NSMessageQueue.MultiplexerFilterInboundMessage(ITransport transport, Message message, Boolean& dropMessage)

Posted elsewhere but can you please share your SQL solutions?

it might help with my DB woes.
Essentially the installation isn't creating the Symantec_CMDB.

I've checked all the usual suspects (perms, disk space, pre-reqs, etc) but I'm guessing I may have missed something...

r

Win2008 R2

SQL 2008 SP1

I got this working on an ESXi VM with 4 GB RAM and 2 vcpus on Windows 2008 R2 build with SQL Server 2008 SP1 (non R2) on box.  Not gone much further than this yet. 

The only issue I have noticed so far, is I didn't have a menu link to the Deployment Portal on the Home menu in the console but I created it instead and it seems to work ok.

My install seems to be working.  I am finishing installing the solutions but the db perms were insufficient.  Attached is a screenshot post install for grins.  My server is altiris-ed to the max!  :-) 

Finn,

I just duplicated your problem and I think you must have had your server configured as a domain controller which we cannot install on. Once I removed the DC via dcpromo.exe, I was able to install. However, the error you received was confusing and not worded properly. I'll report this problem to the appropriate development team. Thanks.

Mark,

Have you tried clicking the 'Check install readiness again' button after having fixed the problem via the automatic fix? After clicking the 'auto fix' link, the readiness checks should be automatically run again but in your case perhaps they didn't. If the problem still persists, I'd be interested in seeing screenshots of your Install Readiness Check screen and Server Manager window (particularly the role services section under Web Server). Thanks.

Mark,

Are you still having this problem? It may be due to bypassing the readiness checks which you alluded to in your previous post. It would be helpful to see the log file from that time if available. SIM logs can be found in the temp folder or the NS logs found in the c:\programdata\symantec\smp\logs folder.

Ricodjs,

Could you attach the log file in which this problem is manifest? Thanks.

Pro.gti,

This is working as designed. Deployment portal is no longer available on the Home menu. All deployment activity is now done in a new feature called Activity Center which can be viewed by navigating to Manage|Computers in the console.

Ryan,

Could you attach the log file that contained this information? I'll take a look and try to find a solution for you. Thanks.

Anyone tried Installing Workflow yet?

I cant get past creating the database

I think I have given all the rights it needs but keep getting errors.

Here is the final one I can't get past

I cannot get workflow downloaded to save my life.  Not sure what is going on there.  I guess I am going to have to get our network guy to check out what is going on.  Is there a direct link to download the MSIs so I can test where my problem is?  I got CMS, Asset, and SMS installed but I cannot get ITSM downloaded and installed.  Thanks.

It was a database permission issue.  I got more permissions and ceased to have an issue.

I was hung up on SSL configuration, because it seemed to force the use of it.  My IIS setup was not configured for SSL nor did I install any certificates before initiating the install.

When you get tot he web config page of the SMP installer, you can check a box for the NS to use SSL and there is a drop down for the certificate (self generated or choose one).  If you do not alter either of these it says click cancel to proceed without using SSL (if I recall correctly).  However, the UI does not move past that step, so it appears to be forcing you to configure SSL.  To get past this step I chose a self signed certificate and the installation continued normally.  Also, I not sure how it would behave if an SSL cert was already installed— does an already installed certificate show up in the drop down?

This whole part of setup is very confusing and should be changed so it is clear how it is being set up.  The ironic thing is when we go to production we will definitely be using SSL, so I applaud that this is now part of the setup process.  I just think the current implementation is confusing.

Is it not possible each problem be post as separate

• forum "question" easier to mark "solved" ?
• If you provide something to download, publish a "download",
• if some Ideas or suggest: create an "Idea"
• And if you just want to talk: creat a "Blog" entry...

Instead of current spread out everthing in a forum "stack" everything mixed in a glorious melpot. I Know we are now in "non structured" phase for "information". but it is not necessary to make such a mess.

Pascal,  Susan actually asked us to post the issues here if you read her original post.  If there were a dedicated Beta forum it would make more sense but there isn't.

You can mark your posts as private to members of a group but I think many people do not understand that (I didn't until about 5 minutes ago).

Can you be a little more specific?

Could be of interest for others...

I'd rather have a data-mess where anyone can read/learn something from as private messages where only one induvidual can learn from...  That is what fora are all about, ain't it?

My first CMS7.1 installation went fine and smooth using VmWare WS7.1 with an host of W2K8R2-std.  I used the build-in SQL2K8R2 installer. 

Only point where I "lost some time"  was the SQL server choice...  When SQL is installed locally (and also done using SIM) it should recognize this and fill in the defaults.   But that is a minor.

Going to play with this later this week.

Please let me know if you require windows/sql logs

Thanks

R
 

Attachment(s)

a32.zip   52 KB 1 version

Hi Cory,

Yes I did click on the 'Check install readiness again' button several times, I also rebooted, rerun and tried everything I could think of.  As there were not loads of people complaining about the issue, I assumed it was just me so I reimaged my test box and started again, this time it went through without this issue, so unfortunatly I dont have any screen shots or logs available.

Thanks

Mark.

Hi,

I have just finished with installation Altiris Notification Server 7.1.

I didn’t meet with any problems.

Current performance of Symantec console (respond time) is good but not amazing.

I hope the performance will not decrease when I configure 10 clients on server and enable all availed agents.

My configuration:

HW:

HP ProLiant DL585 G1

4x AMD Opteron 2.20 Mhz

4 GB RAM

4x 72,8 GB 320 SCSI ( RAID 10)

OS :

Microsoft Windows 2008 Server R2

Microsoft SQL Server 2008 x64 SP1

Thanx Symantec team good work

According to the installation manager it was not able to download the workflow msi when I was trying to install ITSM.  It gave me an error with the URL stating it could not be downloaded.  I clicked OK, cancelled the installer, rebooted and tried again.  Same download error.  This time I let it continue and it started installing the ASDK and then it started installing workflow, note previous reports of not being able to download the MSI, but failed during configuration.  I rebooted again after verifying the file did indeed exist in the c:\program files\altiris\symantec installation manager\installs folder. Also this part of the install spawns a bazillion little symantec management icons in the system tray.  They don't go away until I mouse over them or reboot.  I managed to work through it but it might warrant some investigation.  At least the system tray icon warrants looking at I think.

I have at last got a working ITMS 7.1 server now (3rd Time Lucky)

Now I have some comments on the welcome screen, not sure exactly where I should be positing them because it is not strictly Instalation, however there does not appear to be a general bugs section.

After the install was completed, The Welcome to the Symantec Management Console page loaded up.

On the right hard side there are 3 different colour boxes, with numbers to the right of them, but it doesnt tell me what these numbers represent.

Also it is showing the Import Microsoft Active Directory / Import Domain Membership/WINS / Network Discovery as ON, however when I click on each link I can see they are not enabled.

Same thing for Automatic rollout to newly discovered computers again it appears to be on, but when I click on the link I can see it is disabled.

anyone saw this error?

after I installed CMS 7.1 beta succuessfully, I found the altiris agent installation file(AexNSC.exe x86 or x64) missing, I searched this file under folder 'altiris',but none, so I couldn't install altiris agent on new client.

I got this working.

I remembered there was a "How to" doc for installing workflow and servicedesk.

there was on part that stated to NOT install as your service account but another that has full rights.  I tried that and it worked just great right away.

I'm glad you were able to get past this issue. If for whatever reason you happen to install again and see this problem, please let me know as I've seen something similar to it, albeit very infrequently, and I'd like to get it resolved. Thanks!

Hello,

I have successfully installed the beta (the full suite) my first time which was nice to see.  Below is a list of things I have found so far:

- can't type a "0" for purchase cost of software.  This is in the silverlight screen called "Add license purchase".

Ricodjs,

I think you've got the same issue posted in another forum as well. So that there is no confusion, I'll follow it in this forum from now on.

It appears that the config file in question, coresettings.config, was never extracted from the MSI that uses it. I've never seen this in any of the installs that I've done. In order to recreate that config file you could simply run the MSI that extracts it, however, I'm unsure which MSI contains that file. I would think that it is one of the "altiris_ns*" files, perhaps altiris_ns_7_1_kb53309_x64.msi. But when opening that file in Orca and browsing through the Property table, I don't see that config file listed. I'm going to continue to look into this but for the time being you might try the following in the Windows Run command:

msiexec.exe /i <path>\altiris_ns_7_1_kb53309_x64.msi skipaim=1

This will re-install the MSI and extract any config files it uses but will not configure the product. You would then want to run SIM and do a repair of the platform or reinstall. I'll let you know what else I can find.

The files for all solution products in the suite are located in the same place and are not accessible for direct download. So, if you were able to get files for the products in CMS, AMS, and SMS, then you should be able to get the files for the products in ITMS. I would guess that this might be a network issue. Are you still having problems with this?

Looking at this from the point of view of a new user and installing ITSM -it's a bit of an uphill struggle.

So, I've got a freshly installed 2008 R2 box. I've installed SQL 2005 SP3 (x64) and  I've applied my Windows updates. Am now excited as I'm ready to install the Symantec Installation Manager. As a server administrator, here is my thought process through the install...

1. SIM Installation (great)
   I get an info box that the .NET Framework 3.5SP1 is not present, and would I like setup to install it. I click yes, and to my relief within seconds the work is complete through the valiant efforts of a  DISM script which enables this feature. 
   
   I am impressed. I have not been directed to resolve this myself, it's happened automatically. I like that. A lot.
   
   Within a few more 'next, next' clicks, SIM is up and running. Again, I like.
    
2. Starting the Install (small niggle)
   After some beta-ry goodness, I get up a nice simple option to install Asset Management Suite, Client Management Suite, IT Manaagement Suite or Server Management Suite. I click a few, read the text and find out to my surprise that IT Management Suite it really all of the others put together. That's not really apparent from the interface -the interface makes them look separate. I feel self-doubt creep in.
   
   I click on "IT Management Suite" the thinking being that more is better, then hit next.
    
3. Optional Installations (great)
   The available components screen is really clear. I like it. Documentation is automatically selected too. I probably won't read it, but its nice that it's ticked anyway. I know now that there is documentation, and this will be available somewhere once the install is complete.
    
4. Contact Details (small niggle for non-US residents)
   All OK here, as long as you figure out that as a non-US resident you have to select a fake state before selecting your non-US country, after which you enter something a little more appropriate in the state/province box.
    
5. Install Readiness Check-the Red Xs (pretty good)
   At this point I am told that I need to activate something called WCF,  that IIS could not be stopped/started, that IIS is not installed (isn't that related to the previous red cross??), and that ASP.NET isn't installed.
   
   Luckily, the WCF thing can be resolved with a click, so I click and wait for the fix to compelte (which then begs the question why I am presented with this box anyway??!?)
   
   I can also click to resolve the IIS problems too. This takes a bit longer, but in the end works fine. (Incidently, when IIS was previously installed SIM had some problems recognising that I had installed the IIS6 pieces as well. Will retrace my steps on that one to see what happened) 
   
   They key thing here that I like is that SIM can resolve each readiness shortcoming with a click. This is how it should be, and I like it.
    
6. Install Readiness Check -the triangles (the cumbersome plugins)
   In my recommendations list I now have Sun Java, Microsoft Silverlight v4 and Adobe Flash Player 10. These have links to resolve, but it isn't a point and click apply the fix like before. Here they have to download through IE the plugins, and with Sun Java and Silverlight you'll hit the problem of the IE blocking the download but without the easy option of just adding the site to the trusted list.
   
   To get out of this problem, adding http://download.microsoft.com and http://*.sun.com to your trusted sites will get you through.
   
   Adobe Flash Player, as the link points directly at an executable you get automatic option to add the site to the trusted list, so that's rather less painless.
   
   In short, this section is cumbersome. I really wish this were a bit slicker. Maybe adding the trusted zones automatically?
    
7. Notification Server Configuration (Service/admin Account niggle)
   I'd dearly love to be able to enter a non-admin account here. Have a best-practice install from the outset. Have SIM configure all the privileges the account needs (just like Microsoft do for SQL Server).
   
   At the moment though, I'll create a new admin account. Most people will just put in administrator here and have done with it.
    
8. Notification Server Configuration (cert options misleading?)
   This section is straightforward with the exception of the certificates. The fact that there is a check-box for using SSL makes you think that not using SSL is possible. It doesn't in fact appear to be possible to continue without using SSL, so the SSL option is possibly redundant? The certificate section here should perhaps then be limited to just the option of using an auto self-signed cert or a pucker cert.
   
   Or if SSL really is optional, then the interface should be clearer on this.
   
   When we click 'Next' to move on, we are also warned that the application pool hasn't been set correctly to the Classic .NET App Pool. I'm personally think that is a bit verbose now -this stuff should just happen and be logged. I'm not sure why we need to know explicitly now that the app pool is going to be set to classic.
   
   If we now click back, we can uncheck the SSL options. Click forward and we're OK (whereas before we couldn't proceed unless SSL was configured). Now self-doubt creeps back. Have I now gone into strange code fork, and will using ITSM without configuring SSL give me a problem?
   
   I cross my fingers and click next.
    
9. Database Configuration (good)
   This screen seems clear to me -perhaps because its familiar to NS6. I click next, the connection is verified and then I'm good to go and hit begin to start installing my 107 components which make up ITSM.
   
    
10. The ITSM Install (good)
    The installation progress is very well presented. Overall progress as well as letting you know exactly what is installing. Bars are moving on the screen, which gives confidence that stuff is happening in the background.
     
11. Licenses (OK)
    The license screen is very clear, and the button to install licenses easy to see and well placed. 

In the end though, it all worked.

For reference, my virgin 2008 R2 Server with SQL 2005 SP3 and ITSM 7.1 ended up using using a total of 27GB of my primary partition. My single 3GHz processor (woefully underspec'd) is about 30-40% utilised, and pretty much all my 4GB of RAM is being eaten.

Will add a processor and maybe a couple of gigs of RAM tomorrow... ;-)

I tried direct download from my workstations but it wouldn't let me.  That doesn't mean it wasn't blocked.  I checked and the file actually had been downloaded already so I am not sure why the installer was saying it couldn't download it when it was already there.  Maybe it was saying it couldn't overwrite the file?  That would at least make some sense.  I restarted the installer and chose just workflow by itself and got it to install so the answer to your question is no I am not having problems with this anymore.  Thanks for following up.

Hi Sean.

As I know, very similar issue once has been reported for the installation of ITMS suite to the non-default path. Could it be your case? If yes - please try to install to the default location and check if this will resolve this problem.

Thank you,

Alex.

I have also hit the issue Alon is describing. The issue is somewhat more general than stated. On "Add a license" screen in the silverlight interface, the purchase cost and license quantity boxes in the dialog will not accept zeros in any digit. Twenty was not an acceptable quantity but twenty-one was. The same thing is true of purchase cost values. I could enter 2999 but I couldn't enter 3000. I was able to paste in values which included a zero. Very odd.

During the install I see a fair few  event log warnings/errors. The last entry in particular is swamping my event log.  In chronological order they are,

• Warning: TMInstallMain
  There are a couple of instances of this;
  "Couldn't get the application identity for the Altiris service AtrsHost.  Service credentials will not be set"
  
  "Couldn't get the application identity for the Altiris service ctdataloader.  Service credentials will not be set"
   
• Error: LogicBase.ServerExtensions.exe
  "Error,Monday, October 18, 2010 3:46:17 PM,Unable to set SSL trust System.Exception: File not found: 'unable to get path'
     at LogicBase.Framework.utilities.SSLTrust.InitiateSSLTrust()"
• Error: LogicBase.Local.TaskTrays.exe
  
  Error,Monday, October 18, 2010 3:46:25 PM,Unable to set SSL trust System.Exception: File not found: 'unable to get path'
     at LogicBase.Framework.utilities.SSLTrust.InitiateSSLTrust()
   
• Warning: System.ServiceModel.Install 3.0.0.0
  I get a slew of these following the IT Analytics Upgrade
   
• Error: LogicBase.ServerExtensions.exe
  Error,Monday, October 18, 2010 4:31:20 PM,Enterprise Management Remote Server Role Discovery: Unable to find registry key. Server=ICT-NS7BETA, Key=Software\Wow6432Node\TransparentLogic.com\Ensemble 2006
   
• Warning ASP.NET 2.0.50727.0
  Request Abort
   
• Error: LogicBase.ServerExtensions.exe
  Error,Monday, October 18, 2010 4:54:55 PM,error invoking DoInvoke in service http://ICT-NS7BETA/Altiris/Workflow/ServerMonitoring.asmx
   
• Error: LogicBase.ServerExtensions.exe
  Error,Monday, October 18, 2010 4:54:56 PM,System.Exception: exception invoking method ---> System.Net.WebException: The request failed with the error message:
   
• Error: LogicBase.ServerExtensions.exe
  Error,Monday, October 18, 2010 5:15:59 PM,error invoking DoInvoke in service http://ICT-NS7BETA/Altiris/Workflow/ServerMonitoring.asmx
   
• Error: LogicBase.ServerExtensions.exe
  Error,Monday, October 18, 2010 5:16:03 PM,System.Exception: exception invoking method ---> System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.
   
• Error: Application Error
  Faulting application name: AeXNSAgent.exe, version: 7.1.5357.12357
   
• Warning: MSSQLSERVER
  A few THOUSAND of these. About every 30 seconds I see,
  Login failed for user 'IIS APPPOOL\Classic .NET AppPool'. [CLIENT: <local machine>]
   

Don't know how critical any of these are -guess I'll find out as the beta progresses... System installed as per my entry above on SIM. In short full ITMS install on virgin server with local SQL 2005 x64 installed.

Anyone else seeing this?

Is there any way to define proxy settings to installer.

I tried registry editing, defining proxy in IE.

error text: "Couldn't connect to the Internet..."

I have no direct access to Internet from testlab.

OS: Win2008 R2 Standard

Thanks in advance!

A few errors in the Altiris Logs.....

1. Boot Disk Creator Package Errors
   The vast majority of Altiris log errors are due to package snapshot refreshes. The BDC driver packages,
   
   BDC Driver Package for Win PE x86
   BDC Driver Package for Win PE x64
   BDC Driver Package for Linux x86
   BDC Driver Package for Linux x64
   BDC WinPE Drivers(x86)
   BDC WinPE Drivers(x64)
   BDC Linux Drivers(x64)
   BDC Linux Drivers(x86)
   
   are configured to bdc paths ending in \Drivers\Custom, and these don't exist. This results in mass of errors from various sources such as Altiris.NS.StandardItems.SoftwareDelivery.SWDSupport.ManageDistributionPoints, PackageItem.OnSchedule & Altiris.NS.StandardItems.SoftwareDelivery.SWDSupport.MapHttpVirtualDirectory
   
    
2. Altiris.NS.ContextManagement.DatabaseContext.Dispose
   These errors are the next most common, and have the text "Unexpected error during dispose of database context object (finaliser)!". Sounds bad.
   
    
3. Agent
   A bundle of these which although are filed under 'error' have the text "Failed fo create TaskServerHandler: The operation completed successfully."

I'm probably a muppet, but I can't for the life of me find how to access the service desk. Can someone help me out? I've installed the whole of ITMS 7.1, and I can see in SIM that "Symantec ServiceDesk Solution" is installed.

Ian

Expect you'll need to download and copy the service desk package onto the dedicated 64 bit server you will have created for this and then run it. The SIM will say it's installed but thats just the link in NS to the download capability not the actual package itself.

Steve

Thanks for being patient Steve. I now recall you've told me this before too...... ;-)

I seem to be having the exact same issue.  I have clicked it time and again, clicked on Check Install Readiness (and I know it's working because it refreshed the other requirements, like Silverlight, Java, etc).  Any ideas - I really don't want to rebuild.

C:\Users\svc-AltirisAMS>cscript %systemdrive%\inetpu
et w3svc/apppools/enable32bitapponwin64 0
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights rese

Permission denied
ErrNumber: 70 (0x46)
Error Trying To Get the Object: w3svc/apppools

C:\Users\svc-AltirisAMS>%systemroot%\microsoft.net\F
_regiis.exe -i
An error has occurred: 0x80004005 Unspecified error

I removed IIS and reinstalled it and then it worked.

Hi Ajrat.

I'm not sure, if this solution will be suitable for you, but you may try to install Symantec Installation Manager to some 2008.R2 computer with the Internet access and instead selecting "Install new product" select "Create Installation Package" (last link on the initial SIM dialog). Proceed with the package creation selecting the product you wish to install in a test-lab. The result should be the self-extractable archive file. This file could be transferred to the test lab and used for the installation.

Regarding the proxy: we have complains it does not work as expected; current status of this issue is "fixed" but I'm afraid this fix is not in beta build.

Cheers,

Alex.

No idea if I should keep posting this kind of stuff. Will keep doing it until someone asks me to stop.....

Today I've tried pushing the Altiris Agent to a Windows7 x64 machine. It works fine (as long as you've enabled the admin shares -see http://support.microsoft.com/kb/951016) but....

1. Interface 'Experience'
   Personally, I'd like to have seen this side of the interface improved -missed opportunity here? Separate tabs for manual push and scheduled pushes would have been cleaner -this tab just looks cluttered to me. I know there is a drive to see all the information on one page without clicks, but there are other ways....
   
   Also, with the interface improvements with Silverlight, some live feedback on pushes would have been a very nice touch (rather than having to drill down and click for refreshes). 
    
2. Duplicates -Bug?
   After pushing the agent to the windows 7 box the computer appeared in the database as a both a managed and unmanaged PC -two identities.
   
   I suspect that having to use the push mechanism several times (while I troubleshooted the UAC ) is the reason for the duplicate.
   
   However, I love the fact that managed PCs have different icons from unmanged ones. 

Is Windows7 supported?

I enabled the PCanywhere plugin for rollout and although fine on Windows XP, its not working on my Windows7 x64 Enterprise machine.

Looking in the Agent Window, the install exits successfully with return code 0 -nothing however is installed on the machine. Running  pcAClientInstallManager.exe directly (the program referred to in the SWD task) results in program compatibility errors.

Running Symantec_pcAnywhere_plugin_installer_x64.msi doesn't seem to resolve this issue either.

If you see the problem again, try and run aspnet_regiis.exe from the command prompt. It may return an error indicating it failed to initialize for some reason. The reinstall of IIS may have resolved that.

I've spoken with the dev team and there is a possibility that this could be a timing issue if you are running on a slow machine. The problem should resolve and continue with the install. However, there are two things you can try:

1. Run msiexec.exe with the repair option (/f, I believe) on the .msi that I mentioned in a previous post. This should lay the files back down.

or

2. Run msiexec.exe using the /a switch to do an administrative install which will extract the coresettings.config file to a specified path. Then copy the .config file to c:\programdata\symantec\smp\settings.

Again, I've never seen this issue reported up to this point and have not experienced it myself so I'm curious as to how this happened. What are the specs of the server on which you are installing the product?

Mark,

It appears that the labels associated with the numbers are missing. I'll alert the appropriate dev team to take a look at it. I would think that the 'On' label for the other items would indicate that the links represent policies that are turned on but that doesn't make sense for some of them. I'll follow up on this as well. Thanks for pointing this out.

When I try to open the Log Viewer, I get the following error:

"Windows cannot access the specified device, path or file.  You may not have the appropiate permissions to access the item." 

Same error for the Altiris Profiler.

Hi Randall.

Could you try to right-click to NS Log icon in start menu and select "Run as administrator"? From the first look your problems sounds like a "not enough permissions" situation.

Actually I had tried that already and I get exactly the same message.  FYI -  I am logged in with an account that is an administrator on the box, UAC appears to be working for other things.

Some additional information:

The three numbers that you see in the dialog referenced above refer to (from top to bottom) number of machines discovered, number of machines with agent installed, and number of machines inventoried.

The vertical bar on the left is a measuring stick of sorts that provides a graphical representation of the state of the machines on your network and the color of the bar indicates one of the three statuses to the right.

The links in the box with the 'On' text represent polices that can be enabled(on) or disabled(off). The link for Import Microsoft Active Directory should have the 'On' label rather than the link for 'Import Domain Membership/WINS'.

Hope this helps.

I have tried about 6 times to install SD now with no success.

I get through the base workflow install but when the next window pops up where you get to choose specific SD sesttings, it just sits blank forever.  Anyone get SD installed yet?

EDIT:  

Just tried again after changing some security settings within IIS and this time the 2nd wizard jsut does not even appear.

Dear Symantec:

Please provide an installation guide for ServiceDesk on ITMS 7.1

Yours truly,

Bill

I am confirming that I have the same as well.  Consistent issue

I had the first problem which I solved by creating the directories referenced and I have the last problem as well.

Sean, I'm unable to duplicate this. I've installed to a non-default directory and used a non-default website and the package did get installed. Is there anything else about your install that you can share that might shed some light on this? I have seen something similar to this but it was quite some time ago and haven't had a problem since.

Ian,

Regarding item number eight above, you do not have to enable SSL to install ITMS 7.1. It is an option and you should be able to install without enabling it. I think the concern you had was regarding the creation of a certificate (when clicking Next) which is something usually associated with SSL. This is working as designed. You don't have to use SSL but some of the solutions(I don't know which) may require HTTPS communication and even if you are not installing those solutions we require the certificate to be available and thus create a self-signed cert.

Alon,

The first issue you described is already fixed - it will be available in the next beta refresh.  I will take a look at the others you reported with regards to the managed software bits...

Thanks,

Andrew

Cory,

fixed this one , thanks for looking into it.

Reinstalled SQL and reran installation after uninstalling it.

Something must have broken during the original msi installation

Ian,

The pcA agent will install and run on Windows 7. It seems to be working for me. Open the Symantec Management Agent and enable the 'Show internal tasks and packages' in the Options area. You should now see the pcAnwhere Plug-in Install for Windows item in the policy list. Select it and click on the task in the Application Tasks area. This will run the install again. Make sure that you are not doing this while in a remote session with the workstation. If you still don't see the pcA agent icon in the sys tray you'll want to take a look at the logs and see if they can provide some more information. The agent logfiles can be found on the workstation in c:\program files\altiris\altiris agent\logs. If you want to go one step further you can register the diagnostics .dll to get a log viewer of sorts. Here are the steps to do that:

-Open the windows run prompt and enter 'regsvr32' and point to aexagentdiagnostics.dll

-Right-click the agent and select Diagnostics Window. You'll need to click the Refresh button to refresh manually.

hi Cory,

     My VM disk have two drives C and E, I installed it on E, and the installation is successful, have no errors.

     OS: windows 2008 R2 Enterprise Chinese Simple,

     DB: MS SQL 2008 R2 express.

Hi Alex,

    Thanks, I will try later.

Sean

Is it possible to launch the LogViewer.exe directly, not using the shortcut from StartMenu? It should be inside "C:\Program Files\Altiris\Diagnostics"

Actually, I had tried that as well and I still get the same result.

I just tried a fresh install of everything and I'm still getting the same error:

"No idea if I should keep posting this kind of stuff." - for me your posts are very helpful and valuable, so if possible - please keep posting :)

Cheers,

Alex.

The security restrictions on a DC prohibit many web based applications from installing and/or working correctly.

I am glad that it prevents this from happening -but, yet let's write out the REAL reason why it cannot pass go and collect $200.00

I believe domain controllers can become standalone package / task servers....is 2008 R2 supported for these arcitectural components?

Ian, I was able to reproduce a few of these same messages but not all. I got the first warning mentioned in your list and a few instances of the logicbase errors but none of the rest. I'll see what I can do to get some more information for you.

Hi Cory,

I did the usual troubleshooting above -the issue was that the return code was zero when running the task, but pcAnywhere never got installed.

The event log entry we saw at the time was,

 Fault bucket , type 0
Event Name: PCA2

Response: Not available
Cab Id: 0

Problem signature:
P1: pcAClientInstallManager.exe
P2: 12.6.36.0
P3: pcA Client installer which installs plug-in component
P4: pcA Solution
P5: Symantec Corporation
P6: 1
P7: 200
P8: 
P9: 
P10: 

Attached files:
C:\Users\ictst\AppData\Local\Temp\{eda5fe50-3c2e-4bf5-b8dc-2749cb6cb40e}\appcompat.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_pcAClientInstall_c9405630e8bb0d57e71466d246b7cb8185b857_cab_06c3f804

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6702e5d6-dc64-11df-8a59-005056c00008
Report Status: 4 

Hi Cory,

I understand -problem for me was that the interface left me confused and going into loops leaving me a little lacking in confidence as to what I was actually doing.

As I was not alone in this, it might be worth looking at a minor change on this screen to clarify the SLL configuration options?

Kind Regards,

Ian./

Could you post your server OS version and IIS version? 

Hi,

We create log files of installation which is kept at the location

C:\Program Data\Symantec\pcASolution\pcASolInstaller-pcAClientInstallManager-TRACE.LOG

You can attach that log file if you face any problems.

Thanks Nipun for the heads up on the PCAnwhere install log files.

Kind Regards,
Ian./

server 2008 R2

Whatever version of IIS that comes with that.  IIS 7.x

Can Symantec provide an installation guide for Service Desk please?

Is there someone who has been able to install Service Desk as of yet on the Beta?

Sure would be nice to have a document on the installation as the default install does not work. 

I suspect there is some customization required around IIS and likely the database, but without some instruction I cannot get this installed.

We were able to install service desk without much trouble. We did have issues getting it to run properly immediately afterward, however. We got some useful info from symantec that i haven't seen documented anywhere:

"Two settings need to be changed in the IIS manager on W2K8 before installing SD. Select Application Pools > Default App Pool > Advanced Settings, then Set Managed Pipeline Mode to Classic, and Identity to NetworkService"

Not sure it has anything to do with your issue, but even if it doesn't, if you want it to work once you do get it installed, I'd recommend making these changes now because it did mean uninstalling and reinstalling for us.

I tried your workaround but no go on it.  I get the Workflow part done but when the Service Desk config should come up, it is jsut a blank screen.  I can refresh that window and I get the following error

Error Details

Error Message:
The session id ILNApUJL3keTZglLSfKYZg is not valid or the session has timed out

Message Stack:
at LogicBase.Core.Models.Dialog.DialogSession.Load(String sessionId)
at LogicBase.Core.Models.Dialog.ComposerForm.OnPreInit(EventArgs e)
at System.Web.UI.Page.PerformPreInit()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Pretty hard to test this Beta without base documentation for setup

When the session id is invalid, it is usually because we waited too long to start the ServiceDesk configuration after the Workflow server portion completed.  Do you think that may have been your situation too?

Another thing you could check is to open a new browser to

http://servername/SD.Installation.PostInstallWizard/composerform.aspx

No change to setup using that link.  Lots of log errors stating

Error,Wednesday, November 10, 2010 3:02:45 PM,(WebServiceScheduleInvokeDelegate) Error triggering service at http://<Myservername>//sd.articleseventlistener/ScheduleInvokeDelegateService.asmx System.Exception: exception invoking method ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.UriFormatException: Invalid URI: The hostname could not be parsed.

Yahoogle.

Did you guys not test and document a base install of the Service Desk for the beta?

Everyone else ->

Did anybody get SD working on win2k8 x64?

Hi,

   I did get SD working on Server 2008 R2. I am using a domain account to run the services and an off box SQL server. For me the issue with the blank screen with the service desk configuration and install was due to the application installing everything under the DefaultAppPool instead of the classic app pool. I had to manually reassign the applications to the classic pool and then run the rest of the SD install from a new browser window since the original setup had timed out. The result seems to work. I haven't had time to test it extensively but basic create, resolve, close etc. operations are functioning. My recepie was a mishmash of directions and guesses from the forums and the older servicedesk install guides. The key elements for me seemed to be

   UAC off

   Install account and AD service account as local admin

   Run IIS app pools as AD account

   Do not register the built in app pool accounts with the database

   Make sure all applications are installed under the classic app pool (move manually if necessary)

   Install during the correct phase of the moon

I have the workflow designer installed on the same box and I am still seeing various permission oddities even with UAC off. I would really like to see Symantec clean up the UAC issues before this gets out of beta. The server security people really would prefer UAC on and some of the other settings above also give them serious issues. I would particularly like a document on the permissions that are actually necessary for the AD service account since the settings above are running this with way too much access to the system.

I swear I have tried all of that 3 times.

Note: I am doing an off box Service Desk and off box SQl from my SMP

Yes I agree there SHOULD be a document if Symantec wants us to test this.

 I have spent nearly 3 business days (non billable) trying to work this out.  Being a consultant, I cannot spend anymore time on this unless I am confident that I have complete instructions. 

Now the Beta had been out for weeks and I can only imagine a very small percentage of people have been able to get an install done on Service Desk.  How can this help Symantec test this?

Symantec ->  We volunteer to test this.  Please provide some documentation