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.

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

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!  :-) 

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.

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).

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.

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

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.

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.

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.

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".

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 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/ServerMonitori...
   
• 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/ServerMonitori...
   
• 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?

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

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.

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.