May 27, 2010 - Virtualization    Comments Off on VMware ESX server – Update patches to Critical Baseline

VMware ESX server – Update patches to Critical Baseline

To do this, connect to the Virtual Center using the vSphere Client.

Before making any changes, place the server into Maintenance Mode.

  • In the Hosts and Clusters section, click the Update Manager tab
  • Right-click on an ESX host server and select Scan for Updates
  • After the scan, right-click the server again, and select Remediate…
  • Check the box for the desired baseline, and click Next to run through the wizard

Note that the server may reboot several times and appear unresponsive during the update process.

May 27, 2010 - Linux    Comments Off on Ubuntu Linux and ROOT account

Ubuntu Linux and ROOT account

In a Linux installation, the administrator is known as root and usually has it’s own password. Most operations that need root privileges will ask you for the root password or if you are working on the command line, you would swap to root for a time by typing su (for Super User) and then the password. This gives an element of protection and security to the system.You are advised not to work as root under normal operating circumstances. This is one of the ways that Linux helps protect you from virus infections and other problems.

Ubuntu is a little different and you need to understand the differences if you are to get the best from your system. When Ubuntu Linux is first installed, a normal user account is set up along with a password. When certain operations are attempted – for example going to synaptic package manager – you will be asked for your password. This is your normal user password. If you are working on the command line some operations will require su type privileges. In these instances you need to type sudo before the command and you will again be asked for the password. If you need to have a dedicated root account there is a way of setting one up, but for normal use you wouldn’t need that.

May 27, 2010 - Geeky General    Comments Off on Deploy software with MS System Center Essentials

Deploy software with MS System Center Essentials

Greg’s Weekly quickTip: SCE — Rollin’ Out Software
By Greg Shields

Last time we touched on only the surface of System Center Essentials’ capabilities for inventorying the small network environment. We also talked about how running client tasks from the management interface means less roaming the halls for harried administrators. Read more »

May 27, 2010 - DotNetNuke    Comments Off on Installing DotNetNuke 4.5.5 Locally

Installing DotNetNuke 4.5.5 Locally

[i:30nv73ko]By Mitchel Sellers[/i:30nv73ko]

Source:
[size=85:30nv73ko][URL=http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/119/Installing-DotNetNuke-455-Locally.aspx]http://www.mitchelsellers.com/Blogs/tabid/54/articleType/
ArticleView/articleId/119/Installing-DotNetNuke-455-Locally.aspx[/URL][/size:30nv73ko]

Installing DotNetNuke can be somewhat difficult at times, therefore I am writing this article to give you a full step by step guide to installing DotNetNuke on a Windows XP Pro system. The instructions are similar for Windows 2000 and XP Home but might vary slightly, I have tried to note as many differences as possible. Windows Vista installation is similar but requires a few different steps relating to IIS. This article is a re-visit to my first article of this type geared towards DotNetNuke 4.4.1..

Prior to following this instruction guide please ensure that you have downloaded the "install" version of DotNetNuke 4.5.5 from [url=http://www.dotnetnuke.com/:30nv73ko]http://www.dotnetnuke.com[/url:30nv73ko]. You can save the zip file to your desktop for the time being. You will also need to have SQL Server Express 2005 installed, (Other versions work, but these instructions might not match 100% on other versions). Lastly you must be logged in to your machine with administrative permissions.

The setup will be broken into the following 3 sections; creating the needed SQL Serveer database and user account, unzipping DNN and configuring the web.config file, and finally setup of the virtual directory and starting DotNetNuke.

[size=130:30nv73ko]Creating SQL Server Database[/size:30nv73ko]

[list:30nv73ko]
[*:30nv73ko]Start SQL Server Management Studio Express (SSMSE), (if you don’t have this please install it from [url=http://go.microsoft.com/fwlink/?LinkId=64064:30nv73ko]here.[/url:30nv73ko])[/*:m:30nv73ko]
[*:30nv73ko]Once SSMSE has opened, please note the "Server Name" of the server that you are connecting to, this is the full text of the information in that field. (Circled in below picture) [/*:m:30nv73ko]
[*:30nv73ko]Once you have connected and opened the utility you will want to expand the node for your server name as located in step 2[/*:m:30nv73ko]
[*:30nv73ko]Right Click on the "Databases" node and select "Create New Database"[/*:m:30nv73ko]
[*:30nv73ko]Specify a name for your database, I will use DotNetNuke455 for this example, then click create [/*:m:30nv73ko]
[*:30nv73ko]Now expand the "Security" node, then right click on "Logins" and select add[/*:m:30nv73ko]
[*:30nv73ko]Provide the information for the dnn account, be sure to select "SQL Server Authentication" and remember the password. (If SQL Server Authentication is not available see [url=http://www.hostmysite.com/support/vps/windows/mixedmode/:30nv73ko]this[/url:30nv73ko] to enable mixed mode on your server) [/*:m:30nv73ko]
[*:30nv73ko]Now select "User Mappings" and check the box next to your newly created database at the top, then select the "dbowner" role from the listing at the bottom, this maps the account to have full access to your database. [/*:m:30nv73ko]
[*:30nv73ko]Click "Create" to have your user account created. Once this is completed you are now done with the databse setup. Please remember the database server name from step two and the username and password used to create the SQL Server account as we will be using this in the next section[/*:m:30nv73ko][/list:u:30nv73ko] Unzipping and Configuring DotNetNuke

All files from the DotNetNuke install zip must be extracted to a common folder, typically this folder is created as a sub directory of C:\inetpub\wwwroot. The instructions below will be based on installation to this location, if you desire to install DotNetNuke at a different location simply substitute your folder path anytime it is referenced in the below instructions.
[list=1:30nv73ko]
[*:30nv73ko]Using windows explorer navigate to c:\inetpub\wwwroot, then right click and select "New" -> "Folder" and create a folder called "DotNetNuke455". This folder will become the install directory for DotNetNuke[/*:m:30nv73ko]
[*:30nv73ko]Right click on your newly created file and select "Sharing and Security"[/*:m:30nv73ko]
[*:30nv73ko]Switch to the security tab, if you do not see the "Security" tab, you will need to disable the "Use Simple File Sharing" option in your Folder View Options.[/*:m:30nv73ko]
[*:30nv73ko]Click "Add.."[/*:m:30nv73ko]
[*:30nv73ko]In the textbox type ASPNET if on Windows 2000/XP or NETWORKSERVICE if on Windows 2K3/Vista, then press ok[/*:m:30nv73ko]
[*:30nv73ko]Under permissions for this account check the box for full control, then press "Ok" to save the changes[/*:m:30nv73ko]
[*:30nv73ko]Open the DotNetNuke 4.5.5 Install Zip package[/*:m:30nv73ko]
[*:30nv73ko]Select "Extract All Files/Folders" [/*:m:30nv73ko]
[*:30nv73ko]For the extraction location select the folder you created in step 1[/*:m:30nv73ko]
[*:30nv73ko]Once all files have been extracted you need to edit the "Web.config" file located in the root of the DotNetNuke folder[/*:m:30nv73ko]
[*:30nv73ko]Modify the circled sections of the web config, you will need to set this up to connect to your database, so substitute your values for "Server", "Database", "uid", and "pwd". This format of connection string will work for both SQL 2000 and SQL Express. You may use other valid connection string settings, you may visit [url=http://www.connectionstrings.com/:30nv73ko]http://www.connectionstrings.com[/url:30nv73ko] for assistance with other formats
[img:30nv73ko]http://www.mitchelsellers.com/Portals/1/Articles/Images/web_config_Settings.jpg[/img:30nv73ko][/*:m:30nv73ko]
[*:30nv73ko]Also inside the web.config look for a setting called <add name="AutoUpgrade" value="True" />, change the value on this to "False"[/*:m:30nv73ko]
[*:30nv73ko]Lastly inside the web.config look for a setting called <add name="UseWizard" value="True" />, change the value on this to "False"[/*:m:30nv73ko]
[*:30nv73ko]Save the modified document[/*:m:30nv73ko][/list:o:30nv73ko]
The above finishes the actual configuration of the DotNetNuke file system first we created the needed directory, then we assigned the proper file permissions, then we configured the web.config file to not only connect to the database but to also do some preventative settings changes to secure the site.

[size=130:30nv73ko]Setup Virtual Directory and Start DotNetNuke[/size:30nv73ko]

Now that we have the database and file system setup we will proceed to the final step of setup, configuring IIS to host your website.
[list=1:30nv73ko]
[*:30nv73ko]Open the IIS Snap-In tool, this can be found via "Start" -> "Settings" -> "Control Panel" -> "Administrative Tools" -> "Internet Information Services"[/*:m:30nv73ko]
[*:30nv73ko]Expand the root notes until you can expand the "Default Web Site" node
[img:30nv73ko]http://www.mitchelsellers.com/Portals/1/Articles/Images/IIS_Tree.JPG[/img:30nv73ko][/*:m:30nv73ko]
[*:30nv73ko]You should see your application folder listed under the "Default Web Site", right click on the folder and select "Properties"[/*:m:30nv73ko]
[*:30nv73ko]On the first tab, click the "Create" button next to the application name, you should then see DotNetNuke455 listed
[img:30nv73ko]http://www.mitchelsellers.com/Portals/1/Articles/Images/IIS_Directory_Properties.JPG[/img:30nv73ko][/*:m:30nv73ko]
[*:30nv73ko]Now, switch to the "Documents" tab. Remove all current entries and add "Default.aspx" to the listing. Your window should look like the following when complete.
[img:30nv73ko]http://www.mitchelsellers.com/Portals/1/Articles/Images/IIS_Document_Properties.JPG[/img:30nv73ko][/*:m:30nv73ko]
[*:30nv73ko]Now, switch to the "Dierectory Security" tab[/*:m:30nv73ko]
[*:30nv73ko]Click "Edit" in the "Anonymous access and authentication control"[/*:m:30nv73ko]
[*:30nv73ko]Ensure that a checkmark is included in the "Anonymous Access" box at the top of the screen then click "Ok" to exit[/*:m:30nv73ko]
[*:30nv73ko]Now switch to the "ASP.NET" tab and ensure that "2.0.50727" is selected for the ASP.NET version[/*:m:30nv73ko]
[*:30nv73ko]Click "Ok" to save your changes and complete the IIS setup[/*:m:30nv73ko]
[*:30nv73ko]Now open Internet Explorer and navigate to "http://localhost/DotNetNuke455/Install/install.aspx[/*:m:30nv73ko]
[*:30nv73ko]You should see some test indicating the DNN installation progress then a link that says "Click here to access your portal"[/*:m:30nv73ko][/list:o:30nv73ko]
This walks you through the entire setup process to get a local copy of DotNetNuke working with SQL Server 2005 Express. This installation guide can help you get up and going on a hosting provider as well, simply noting that the first portion of the setup is typically completed by your web hosting provider.

Pages:«1...25262728293031...61»