Happy July 4th – Read the Constitution and Deceleration of Independence

July 4th is tomorrow and for those in the United States it is the day we celebrate the United States declaring itself independent from Great Britain.  Before you head out to your picnics, fireworks, and family get together, please take time to read the two most important documents in our country’s history: the Declaration of Independence and the Constitution.

Full text of the Constitution can be found here

Full text of the Declaration can be found here

The preamble of Constitution sums everything up:

We the people of the United States, in Order to form a more perfect Union, establish Justice, insure domestic Tranquility, provide for the common defence, promote the general Welfare, and secure the Blessings of Liberty to ourselves and our Posterity, do ordain and establish this Constitution for the United States of America.

And the opening of the Declaration of Independence:

When in the Course of human events it becomes necessary for one people to dissolve the political bands which have connected them with another and to assume among the powers of the earth, the separate and equal station to which the Laws of Nature and of Nature’s God entitle them, a decent respect to the opinions of mankind requires that they should declare the causes which impel them to the separation.

Installing the Dell Management Console

Summary:

This article will cover the steps to install and configure the Dell Management Console, including the steps to build a server, requirements for the server and steps for installing the DMC.  

Overview

The Dell Management Console (DMC) is built around the Symantec Management Console and the Symantec Management Platform. DMC allows you to centrally manage your Dell Servers and clients along with managing the OpenManage Server Administration Agent (OMSA). DMC allows you to manage things like BIOS level, Dell specific patches, and allows you to create monitoring policies to monitor the health of your servers. For more information visit http://dell.symantec.com

Requirements for installing the Dell Management Console

The following tables come from the Symantec Planning and Configuration Guide for Altiris Notification Server 7. This document can be found on the Altiris knowledge base, http://kb.altiris.com. The tables are broken up into whether or not you are installing the DMC with SQL on the same box or off box. Also the requirements are for managing under 3000 nodes. Following the requirements for the server, are the requirements for installing the Altiris Agent (the Altiris Agent will then be used for managing, pushing out the OMSA agent, and then creating monitoring policies).

 

Notification Server managing under 3000 Endpoints with SQL on Box

Hardware	Recommendation
CPU	8 Cores
CPU Speed	2.4 GHZ
Memory	8 GB
Network	Gigabit
Disk	10 GB free
Operating System	Windows 2003 Server Enterprise (32-bit)
Software	Recommendation
.NET	Microsoft .NET 3.5
Web Browser	IE 7
Web Server	IIS 6.0

 

Notification Server managing under 3000 Endpoints with SQL off box

Notification Server Hardware	Recommendation
CPU	4 cores
CPU Speed	2.4 GHz
Memory	4 GB
Network	Gigabit
Disk	10 GB free
Operating System	Windows 2003 Server (32 bit)
SQL	SQL Server 2005 off box
Software	Recommendations
Web browser	Internet Explorer 7
.NET	Microsoft .NET 3.5
IIS	IIS 7.0

 

SQL Hardware	Recommendation
CPU	4 Cores
CPU Speed	2.4 GHz
Memory	8 GB
Network	Gigabit
Disk	10,0000 RPM SCSI or better with RAID 1+0
Operating System	Windows 2003 Server Enterprise (64-bit)
SQL	SQL Server 2005
	See Microsoft KB for optimal SQL Configuration

 

Altiris Agent Requirements

Item	Specification
Operating System	Windows 2000 SP4, Windows 2003 (32-bit, 64-bit), Windows XP SP2/SP3, Windows Vista (32-bit, 64-bit), Windows 2008 (32-bit, 64-bit (not core)
Hard Disk Space	60 MB
RAM	64 MB minimum (128 recommended)
Internet Explorer	IE 5.0 or later
Access Rights	Account used to install agent must have local admin rights
Windows XP Items	Turn off simple file sharing, open port 80/445 directed to Notification Server IP

 

Steps for Installing the DMC

Installing the Server

Follow your standard build documents for installing and building a new server. A couple of pieces of software to make sure you need to have. IIS and ASP.net need to be installed and enabled. The easiest way to do this is through the “Configure Your Server” wizard and turn the server into an Application Server. .NET 3.5 needs to be installed, an important note is to NOT install .NET 3.5 Service Pack 1. IE 7 needs to be installed as well.

If you are going to be using SSL (HTTPS), please install and configure IIS to use SSL before installing DMC. If you try to make this change after the install, there will be problems within the system.

If you are running SQL Server on the same box, please install this and configure it correctly before proceeding to the next steps.

The Symantec Management Console is installed under the Default Web site which will cause problems if you have other web servers running on the DMC system.

Installing SIM

The Symantec Management Console utilizes the Symantec Installation Manager (SIM) to install all parts of the Management Console. SIM can be downloaded from the Symantec Website (http://www.symantec.com/business/products/trialware.jsp?pcid=pcat_infrastruct_op&pvid=cm_suite_1). Once this is downloaded launch the executable and you will be greeted with this screen:

Select Next and you will be presented with the directory to install SMC into. A quick word of warning, the directory you select here is the directory all of the Console will be installed to.

Once the installation is finished, the Symantec Installation Manager will start allowing you to install other portions of the console.

Installing the Symantec Management Console

When the Symantec Installation Manager is launched it will be default open up to Install New Solutions. While you can install both the DLP component and also the Management Console at the same time, I recommend installing just the Console and then the component.

From the Installation Manager scroll down until you find the Symantec Management Console

After selecting “Review selected products” and then Next, aceept the license agreement and continue. Fill out the required information. This information is required to verify export controls.

After the information is filled out, select Next for the systems requirement check

The Symantec Management Console requires ASP.net, IIS, IE 7.0, at least 2.0 gigs of RAM, and Windows 2003 Server along with MS SQL 2005. As you can see in the screenshot I do not meet the requirements. If you do not, close the Installation Manager and resolve any problems.

If you meet the requirements select Next to begin installation of the Symantec Management Console. While it is not necessary to restart after the installation is complete, I have had the best luck rebooting before moving on to other installations.

Installing DMC

After the Symantec Management Console has been installed, reboot the system. While this is not a requirement, after much testing this provides the best option.

Launch the Symantec Installation Manager from Start – All Programs -> Altiris -> Symantec Installation Manager and launch the Symantec Installation Manager.

Select Install new products and once you find the Dell Management Console from the list

After selecting the DMC, all of the dependencies will be installed as well

Click on Ok to proceed and move on. Once the install is complete we begin installing the Altiris Agent and the OMSA Agent.

Deploying the Altiris and OMSA Agent

 

Discovering Dell Servers
There are 3 ways to discover computers within the DMC, import from Active Directory, domain discover and network discovery.

An Active Directory import is the most reliable discover of all of the methods. An important item to remember is this is just an import, nothing is modified in Active Directory, no schema modification, nothing. To perform the Active Directory Import, within the DMC, navigate to Actions -> Discover -> Import Active Directory. The console will look like the following:

Fill out the correct information and run the import. More information on running the AD import can be found in the DMC Manual.

 

The second way to discover computers is through a domain membership or domain browse. This type of discovery will query the Master Browse list for computers. To perform this discovery, navigate in the DMC to Actions -> Discover -> Import Domain Membership/WINS. The screen will look like the following:

Fill out the correct information and run the discover. More information can be found in the DMC Manual.

The third way of discovery computers is through a network discovery. This can take the longest depending on how large of a discovery you are running. To perform a network discover navigate in the DMC to Actions -> Discover -> Network Devices. The console will look like the following:

Fill out the correct information and run the discover. More information can be found in the DMC Manual.

Pushing out Agents

Once we have discovered Dell Servers we can roll out our agents. The first agent we need to push is the Altiris Agent, and then the OMSA Agent.

To deliver the Altiris Agent, navigate in the DMC to Actions -> Agents/Plug-ins -> Push Altiris Agent

Select the server from the list of computers and select Install Altiris Agent. For more help on the pushing the Altiris Agent, see the DMC Manual.

 

To install the OpenManage Administrator Agent, navigate to the DMC Home Portal and select Deploy OpenManage Administrator.

From this part of the console, select Launch Dell OpenManage Server Administrator Deployment Wizard. Select the computers from the drop down and then hit next. By default the installation of the OMSA agent is scheduled for now. There will be a task at the bottom of the Dell OpenManage Server Portal page that will turn green when the installation is complete.

Sharing home directory between Kubuntu and RHEL5?

I’ve posted previously on setting up my laptop to dual boot between Kubuntu and Red Hat Enterprise Linux 5.3 but have run into one snag, I don’t know enough to fix.

As an aside, I ran into a lot of problems with the program I needed for work running in 64-bit version, so I am working reloading to 32-bit.

What I would like to do if possible, is to share my home directory between the two boxes.  Part of the reason is I use an XP VM and shared folders to work on files in Office 2007 and outside of the XP VM and connect via shared folders.

So my /home/jonathan/Documents folder is configured as a shared folder on VM and then I can write statements of work, and utilize other work related apps, and then if I was sharing my home, I could access the same files whether I am running RHEL or Kubuntu.

Is it just as simple as creating /home in a seperate paritition and using the same username on RHEL and Kubuntu?  Or is there some magical voodoo I need to do?

Hope this makes sense

Symantec Government Symposium Part II

Earlier I wrote about the Symantec Government Symposium, and was just notified that content and presentations are now available online.

For more information including PowerPoint presentations, look here

Symantec Government Symposium – A review

Recently i had the opportunity to attend the Symantec Government Symposium in Washington DC.  This is an event sponsored by Symantec and some of its partners.  About 1500 customers of Symantec was gathered in one building to discuss what is going on in the Federal Space in regards to IT and IT Security.

The symposium started out with an introduction from John Thompson and Enrique Salem.  The former president and CEO of Symantec introduced the new CEO Enrique Salem, who then introduced the keynote speaker Senator Mark Warner, from Virginia.  Mr. Warner has a tech background and understand technology.  However, I was disappointed in the tone of the speech as it seemed more like a campaign speech instead of a keynote speech.  Mr. Warner is newly elected and perhaps that is why it seemed so much like a stump speech.

I attended the track entitled “Secure and Transparent Government.”  The first session in this track was called “Assessing Security Standards Today.”  The roundtable discussion was made up of Erick Hopkins (U.S. Senate Homeland Security and Governmental Affairs Committee), Ron Ross (Senior Computer Scientist and Information Security Researcher, NIST), and Tony Sager (Chief Vulnerability Analysis and Operations Group, Information Assurance Directorate, NSA).  The big take away from this discussion (besides everyone having really really long titles) was in regards to the changes to FISMA (Federal Information Security Management Act).  FISMA was originally passed during the Bush Administration and provides guidance on what branches of the government must do.  From the discussion I learned that FISMA 2.0 will have a lot more “teeth” to it.  FISMA is one new thing I will be learning.

The second session I attended was “Information Security: You can’t secure what you don’t manage.”  The members of this roundtable discussion were Jaren Doherty (Associate Deputy Assistant Secretary, Office of Cyber Security, Directory of Veterans Affairs), Holly Ridgeway (Director, Justice Security Operations Center, Department of Justice), and Pete Stark (Manager, Corporate Information Security, US Postal Service).  I was disappointed in this session, I thought they would have talked more about how to manage these endpoints, why managing the endpoint, etc.  It seemed more discussion about what they did security policy instead of how the endpoints were managed.

The first place to start with a secure endpoint is to have that endpoint managed.  This mantra is something we at ITS have been preaching since we started with Altiris back in 2001.  In fact this mantra is something Mr. Salem himself has talked about when mentioned operationalizing security.  The session was very disappointing.

The rest of the day I spent trying to meet and greet people and to try and get the ITS name out in the public.  It was great to meet potentially new customers and more Symantec sales people to work with.

 

A great event if you do business with the government and with Symantec.  Follow the hashtag #symgovsym on Twitter for more information

Problems getting wireless card to work in RHEL5, works in Kubuntu 9.04

Dear Lazyweb,

I have a Dell Latitude E6500 that I currently dual boot RHEL 5 and Kubuntu 9.04.  I have one small problem.  The Dell hasa a Intel Wifi Link 5100 card in it that works fine in Kubuntu, however I cannot get it to work at all in RHEL5.  lspci shows the card is there, but cannot get to even find my wireless access point to connect.  Wired works fine, but in my study I don’t have any wired connections.

Any hints on what I’m doing wrong?  Pretty new to RHEL so I might be missing some easy.

Thanks

Problems running VMWare Workstation 6.5.1

Reloaded my laptop this weekend w/ Kubuntu 9.04 as I was having problems and am redoing my laptop for dual boot purposes.  Before the reload i had no problems with runing VMWare Workstation 6.5.1, now after the reload I am unable to launch any of my VM’s.

Here is the error:

Failed to open device “/dev/vmci”: No such file or directory
Please make sure that the kernel module ‘vmci’ is loaded.
Module DevicePowerOn power on failed.

Any ideas?  Googling didn’t help out

Installing the DLP Integrated Component in Altiris

Summary

This article is part I of II on the DLP Integrated Component and how it works within the Symantec Management Console (Altiris). Part II will cover using the Integrated Component (IC) to manage your Endpoint Agents. We will discuss installation of the Symantec Management Console and then installation of the DLP Component

Contents

Summary    1

Introducing the DLP Endpoint Agent    1

Installing the DLP Integrated Component    1

Installing the Symantec Installation Manager    1

Installing the Symantec Management Console    2

Installing the DLP IC    4

Introducing the DLP Endpoint Agent

Installing the DLP Integrated Component

Installing the Symantec Installation Manager

The Symantec Management Console utilizes the Symantec Installation Manager (SIM) to install all parts of the Management Console. SIM can be downloaded from the Symantec Website (http://www.symantec.com/business/products/trialware.jsp?pcid=pcat_infrastruct_op&pvid=cm_suite_1) Once this is downloaded launch the executable and you will be greeted with this screen:

Select Next and you will be presented with the directory to install SMC into. A quick word of warning, the directory you select here is the directory all of the Console will be installed to.

Once the installation is finished, the Symantec Installation Manager will start allowing you to install other portions of the console.

Installing the Symantec Management Console

When the Symantec Installation Manager is launched it will be default open up to Install New Solutions. While you can install both the DLP component and also the Management Console at the same time, I recommend installing just the Console and then the component.

From the Installation Manager scroll down until you find the Symantec Management Console

After selecting “Review selected products” and then Next, aceept the license agreement and continue. Fill out the required information. This information is required to verify export controls.

After the information is filled out, select Next for the systems requirement check

The Symantec Management Console requires ASP.net, IIS, IE 7.0, at least 2.0 gigs of RAM, and Windows 2003 Server along with MS SQL 2005. As you can see in the screenshot I do not meet the requirements. If you do not, close the Installation Manager and resolve any problems.

If you meet the requirements select Next to begin installation of the Symantec Management Console. While it is not necessary to restart after the installation is complete, I have had the best luck rebooting before moving on to other installations.

Installing the DLP IC

Once the Symantec Management Console has been installed, install the DLP Integrated Component. To do so, launch the SIM from Start -> Altiris -> Symantec Installation Manager. Once launched the following screenshot will be displayed showing installed products.

Click on “Install new products” to install the integrated component.

From the filter drop down, select “Filter by all” and scroll down till you find the DLP Integrated Component, see the following screenshot.

Follow the same steps, without making any changes you did during the installation of the management console.

When the Integrated Component is finished, launch the Symantec Management Console to begin using it.

Using Skytap for Demoing Altiris

With the release of Altiris 7 and the upcoming release of Service Desk, plus moving into more and more Symantec products we have seen the need for more hardware for demos, videos, and other projects.  However hardware is expensive and something that money can’t be spent on during the current economy we are going through.

One of the engineers I work with investigated moving into “cloud computing”, how much it would cost us and who would be the best company to invest some money into.

The company that we decided to work with is called Skytap and I am loving working with it.  Each month with the contract we have, we have 1000 hours of computing time to use.  Also we have 10 Skytap Virtual Machines we can be running at a time.  A SVM is defined as 1 Gig of RAM and 1 processor.  For a CMS 7 demo of 1 NS 7 box then I consume 3 SVM’s.  3 Gigs of RAM and 2 procs.

My Altiris demos have never been so good or so quick to respond.  All I need is internet access and a web browser and I can provide a kick butt demo.

Let me know if you need more details or information, but I highly recommend Skytap.

Contributing to Ubuntu shouldn’t be just packaging

We have had a lot of discussion on #ubuntu-us-mi in regards to how I can contribute to Ubuntu.  It seems the answer is always “packaging.”  But there are people who can code or develop some missing ingredient to Ubuntu that a person might want to develop.

Let me try to explain, saw this from @dhoolbach on identi.ca

want to learn !ubuntu development and packaging – I need your input: http://is.gd/Of4Q

And it goes back to the discussion we had on the channel.  A new user says “I want to contribute”  And someone responds “Package this app”  But what if they don’t want to package?  They want to contribute code.  The answer then is “Work Upstream” but how does someone go about just that?  Do we explain enough how to work upstream on code/patches/etc?  Please correct me if I’m wrong, but I think we need some howto’s or guidance on how to help solve itches best resolved upstream.

Discuss or correct me if I’m wrong