Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Workflow Solution
Showing posts in English
JGibbs | 12 Oct 2010 | 0 comments

Regional Symantec Platinum Partner looking to significantly expand our flourishing Symantec-Altiris Pratice. Seeking Systems enginerring talent to join our firm. Certifications required (EV, SEP, BE, Altiris)

Please feel free to reach out to me for additional details of position and benefits associated

John E. Gibbs
Senior Technology Consultant
ACP-Arlington Computer Products

800-548-5105 xt 165
Cell; 414-737-6886
jgibbs@arlingtoncp.com

ohzone - CherylPeterson | 20 Sep 2010 | 3 comments

Even in the fast paced world of technology, there are early adopters. When managed IT providers were just a luxury for mega-corporations, mindSHIFT Technologies, Inc. changed the paradigm by offering enterprise environments and expertise to SMBs. Seeking strategies for scalable growth without adding staff, mindSHIFT turned to Symantec for process automation, asset discovery, and client and server management solutions. mindSHIFT is now able to provide proactive support and deliver better customer service through automated processes, and will be able to deploy new software for customers 10 times faster.

Read more here: mindSHIFT Technologies, Inc.

Download the PDF below

KSchroeder | 11 Jun 2010 | 3 comments

Our test and development servers got patched last night, including the IIS patch in MS10-040.  Today when our users went to test, the workflows wouldn't load and there were lots of errors in the Event log.  So, heads up to not install that patch to your Workflow servers.  The MS KB article for the patch (KB982666) and the Altiris KB53303 referencing it notes that it shouldn't be installed unless a prerequisite hotfix KB973917 is also installed.  Symantec is updating the PMImport rules for Patch Management to address this, however the actual patch itself does not seem to verify its prerequisite is there.  Our server guys used an alternative product to deploy the patches.

BRING | 06 Apr 2010 | 0 comments

There have been many questions and concerns about the ability to remove changes, incidents, and problems from the Servicedesk database.  Many build up test systems, customizing workflow components,  portal pages and  reports to meet the specific needs of their environment.  They then would like to just start with a fresh database, unencumbered by old data that is not relevant.  Does this capability exist, and how would it be used?  If not, what are the best workarounds to accomodate this issue?

Unfortunately, incidents can be resolved and closed, and changes and problems come to completion and closure.  But not removal or deletion.   Once the items are in the database they are there for good.  There are feature requests underconsideration to change this.  

Working around this problem, however, should not be too discouraging.  Simply reinstalling the environment is the best workaround,   This...

BRING | 03 Mar 2010 | 1 comment

After reviewing the Servicedesk 7 customization guide (Pages 34-35), and knowing that SLA's (Service Level Agreements) were important for Incident Management, I began my quest to modify the SLA for Problem Management.  I had made all of the changes necessary, and created a few problems from my incident pool.  However, I noticed that none of the due dates or late dates had changed.  Where had I gone wrong?

Well,  as it turns out, I did everything correctly.  Further research showed that, during the development and documentation of Servicedesk 7.0, although not required by ITIL, it was thought that having a configurable SLA for problems might be useful for customers.  So a preliminary implementation workflow was started, and included in the customization documentation. After release and further review, it was decided that, since ITIL does not have a SLA requirement for Problem Management, that this documentation and preliminary workflow...

BRING | 04 Feb 2010 | 0 comments

While running applications from our workflow server, the end users were reporting that emails were not being sent as designed.  We furhter  noticed the following error messages:

EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.3959, P3 45d6968e, P4 mscorlib, P5 2.0.0.0, P6 4a7cd8f7, P7 11eb, P8 18, P9 system.outofmemoryexception, P10 NIL.

An unhandled exception occurred and the process was terminated.
Application ID: /LM/W3SVC/1/Root/HardwareEquipmentRequestV4
Process ID: 1052
Exception: System.OutOfMemoryException
Message: Exception of type 'System.OutOfMemoryException' was thrown.
StackTrace:    at System.Threading.ExecutionContext.CreateCopy()
   at System.Threading._TimerCallback.PerformTimerCallback(Object state

We further noticed additional error messages from the specific project logs:

System.Data.SqlClient.SqlException: Could not allocate space for object 'dbo....

WEVO Group Developers | 03 Feb 2010 | 0 comments

Now with Workflow 7's ticketing and reporting functionality you can add status and reporting to your processes quickly and easily.

I recently had to build a "Proof of Concept" (POC) for a client proposal that we are working on. The client wanted to generate reports using Workflow to track a process for auditing purposes.

Now as many of you know, in past versions of Workflow we would've had to create a report like this in a couple of different ways: we could have developed a Web Forms Reporting Dashboard or a SQL Reporting Services report. Both of these options would have required some significant development time and additional cost to the project.

Ticketing Functionality

Some of the new ticketing functionality that was created for ServiceDesk 7 in Workflow allows us to develop these reports quickly and easily.

I think it is important to note the ticketing functionality wasn’t developed...

Don Rowland | 20 Jan 2010 | 4 comments

I am trying to solidify a group of 10 who can commit to a 2 day training class on Workflow 7.  It will be a complete hands on class covering topics from install to complex design.

We have a commitment from the Symantec Workflow trainer that if we can get at least 10 people to commit, they will bring the class to us.

Each student would need to bring a laptop with at least 3GB of memory and enough space to store the virtual machine for the class material.

I'd like to have this class in February.  Please post and/or e-mail me if you are interested and can commit to attending. 

BRING | 16 Dec 2009 | 1 comment

After successfully installing ServiceDesk 7.0, and passing thru the evaluation time frame, or after applying a production-type license, the following error has been observed.

Error 1:

"License does not allow use of web part [SearchTextPortalWebPart] 

What are some suggested ideas to troubleshoot  this problem, since it makes using ServiceDesk impossible?

1. On the ServiceDesk Server, open up the Notification Server Credentials tool on the ServiceDesk server, and verify that the connectivity test for the Notification Server is successful.
       a.  If not, add the correct credentials and retry.  Suggested credential to use the the Altiris Application Identity (APPID) account.  This account should be a member of the local administrators group on the Symantec Management Platform Server (NS).
2. On the Servicedesk Server, open up the...

BRING | 14 Oct 2009 | 0 comments

While running a Workflow application recently developed, a problem manifested itself in a couple of different ways. There was first an error:

"Server was unable to process request.--->Object Reference not set to an instance of an Object"

Also, no matter how I varied the input information into the application, the result set always matched the result set that I had obtained the first time I ran the program.  It would change if I closed and restarted the Workflow session, or republished the application to the server, and ran it again.  But once running, it did not matter how many different iterations of input data I provided, the result set was the same, and that was frustrating.

Upon further review of my project, and specifically a linked workflow model inside of my project, it was discovered that there were two potential culprits for this behavior.

The first culprit was found within the properties of...