Push the NS Agent with This Simple Workflow
A few of the Workflow Solution beta testers are already showing us that the operative root in Workflow is "work".
Here's a cool example that walks you through the steps necessary to push the Notification Server Agent out using the tools in the Workflow Solution box.
Prerequisites: None
Estimated time to complete: 15-20 minutes
Step 1: Create a new Forms (Web) project.
Step 2: As we will need to authenticate against the NS further down the workflow chain, add the NS Credentials for:
- The Notification Server
- User Name
- Password
- Domain (if needed)
Step 3: Connect the outbound connection of the 'Create Notification Server Credentials' component to the 'End' component.
Step 4: Add the 'Form Builder' Component between the Create Notification Server Credentials' component and the 'End' component.
Step 5: Double click on the 'Form Builder' Component and add the 'Outcome Component' as Path Name: 'Submit'
Step 6: Now let's add a little personality to our form. Click on the 'Select Theme' Icon
Edit Project Theme
Add
And pick one of the many project themes. (Customized small blue oval pictured)
Step 7: Add two labels as shown
Step 8: Add a text box component and call the 'Output Name' "NODE".
Place and expand the text box next to the second label.
Now click "OK" to close the form.
Step 9: Choose the 'Push Altiris Agent To Computers' Component, and place it between the 'Form Builder' and the 'End' Components. Be sure to connect the output connection as illustrated.
Step 9: Click on the 'Push Altiris Agent To Computers' Component, and set the Inputs 'Computer Names; using 'Process Variables', 'Add Single' and Choose NODE.
Finished!
Now either run the project in debug mode, or publish.
I love workflow. I'm
I love workflow.
I'm working to create things like this so that users can self-help with installing applications. Freebie stuff like java, reader, flash or shockwave.
I'm also building some that can install bigger apps like Office and CS3, but I'm hoping to build in some kind of credential check to just make them available to the support staff. Havn't tried yet, but we'll see where it leads.
What's the point?
First off, I really appreciate this illustrated example. My question is directed at the Altiris Workflow Solution, not this posted article.
However, this article does serve as an example why this new Altiris solution appears to be 'reinventing the wheel', rather than 'improving the wheel'.
Why spend the time trying to create a web form work flow like this one when the functionality already exists in the NS web console? This solution appears to be geared towards [web/application] developers who want to dress up existing Altiris functionality in a different suit.
I know this may come across as 'ripping', but I really haven't seen good rationale for investing time and other resources into this new solution. Managing Altiris CMS and AMS is already time-consuming enough.
Sorry that I used your article for my soap box rant, Mr. English. :)
Missing the point - the sequel
Hey dlmcduff,
Don't worry about 'ripping'. This is all about discussion.
I can see where you are coming from, but if you're always working on the engine within Altiris, then you never get to view the cab.
Imagine that you're not working within IT, but HR, and you need to provision a new employee for example... Rather than give this person rights to the console (which can be rather intimidating for someone who has never seen it) why not give them a form to pick and choose from?
Also, this is much much more than dressing up existing functionality. This ties everything together. You can now create 'apps' that can cross the bridges between AMS/CMS... all in one place.
You also have the functionality to expand what already exist.. say you want to add fields to the Parent and Child line items within a purchase request or purchase order within Altiris?.... no can do.. it cant be done within the console without breaking something else, but with workflow, you'd be able to create additional fields and link them to both the PO and purchase request so historical data could be reported on.
We're only seeing the tip of the iceberg here, and I myself have some difficulty wrapping my head around this, however I have a feeling sometime soon down the road that this solution will be adopted by everyone in large enterprise.
Great Example
You know Mike, you give a great example. Part of what we're hoping to do is involve our Vendor in the asset creation process. By exposing just a web form to those guys we can have them fill something out to let us know that an asset is on the way.
The thought would be to then use it to create that asset and an incident that would be sent to our guys handling new computer equipment who would preflight the computer in Deployment server so it would just need to be plugged in and PXE booted when it reaches the site.
Giving an external contact access to our console scares me, but not so much on a form where I can more acurately control what is included.
- Matt
The point is
Creating the things that currently can't be done in an easy way through the NS console and pushing that out to web forms.
You mentioned you use AMS, so create a web form that someone can fill out that creates an incident, checks the status of available licenses, and routes the request for new software the correct way, including moving the computer to the correct approved software collection which would automatically install the piece of software.
Jonathan
Jonathan Jesse
Practice Principle
ITS Partners
I agree with both of you...
I'm not saying that Workflow is an unnecessary tool. I just don't think it should be a new, separate tool. My point is that Symantec Altiris should devote the development time to making a console solution that does allow you to perform tasks that "[can] be done in an easy way through the NS console".
I want to say that I am not against this product. I think that this product is most beneficial to organizations that have the resources (developers) to develop their own [web] applications.
I'm concerned that a product like this will give Altiris an excuse to really (as though it's not rather tortoise-like now) slow down the development of practical workflow functionality and usability "within" the console.
I agree with Mike that this product can be really beneficial to large enterprises that may need customized solutions (like Mike's HR example). But what about us little guys who fork over the bucks for a solution or two, only to be told that we need to purchase an additional solution to develop practical workflows? If this solution was an added component to CMS or AMS, it would be a good deal for all! If you're small, you could create an app or two to address a special need and if you're large, you can have a team working on creating your own portals of self-serve tools or whatever else.
The bottom line is that most people purchased Altiris because they were pitched a suite of software solutions aimed at working with or simplifying the organization's workflows. I just think that it's kinda messed up that we have to purchase ANOTHER solution to accomplish the task of customizing existing products to meet our needs.
David
Would you like to reply?
Login or Register to post your comment.