MARVEL and SPIDER-MAN: TM & © 2007 Marvel Characters, Inc. Motion Picture © 2007 Columbia Pictures Industries, Inc. All Rights Reserved. © 2007 Sony Pictures Digital Inc. All rights reserved.
|
DotNetNuke > EntitySpaces
Saturday, July 22, 2006
|
*EDITED* Some people associated with EntitySpaces have since placed comments and sent me e-mails regarding this post. As with any web site or blog you, the reader, should make up your own mind about things. Since I admittedly have not done 100% research on EntitySpaces, before you use this or any other product, you indeed should perform 100% research before dedicating your time and/or finances to the product.
In case you do not get the meaning of this blog title, DotNetNuke is greater than EntitySpaces. :)
So, since I use the Google Adsense in my blog and whenever I mention DotNetNuke, EntitySpaces ads appear, please do everyone a favor and DO NOT click on the EntitySpaces ads. If you need an online content management system for you business, intranet, home or family web site - then there is only one choice for the money -DOTNETNUKE! Yes, both DNN and EntitySpaces are free, but DNN has a proven track record and we KNOW that they will be around for a while with support and even better community support.
Don't do what I did. I built my own portal. It took 3 months and then DNN was released with more options. Visit DotNetNuke.com today. :)
That sounded like a commercial. Yuck!Labels: DotNetNuke
posted by The Mighty Will @
permalink
 
My Online Family Photo Album is Posted
Saturday, July 15, 2006
|
FYI - The link has been to the right --> for a few weeks now, but as of tonight I have just completed posting all of the newest pictures. Take a look! Enjoy, but don't steal! :)
http://www.strohlsitedesign.com/Gallery/Labels: Family Stuff
posted by The Mighty Will @
permalink
Initial DotNetNuke Setup - Host & Admin Security (Part Duex)
Friday, July 14, 2006
|
While performing some upgrades after finding out that the FCKeditor integration for DotNetNuke has been released, I realized that I forgot something in my original blog on this topic.
While it is best to create the default admin account and host account with names other than the default "admin" and "host" usernames, you should also do one more thing throughout the lifetime of the portal implementation. While for most of you this may go without saying and it may also seem like web development 101 or computer user 101, for others it will not be.
Once your DNN portal is set-up, configured, and deployed, you should only login using the Host or Superuser account when it is required from that point forward. The reason being that everytime you login to the DNN portal, you are sending your login credentials as clear text across the internet. Some of you may be using encryption tools in conjunction with your login form, but if the right bot captures 3 or more of the same login it is quite realistic that your login will be compromised.
I know that many of you are now saying something like, "what are the chances of that?!" You're right to assume that the chances are low, but I rather not live through the hassle of trying to break into the DNN portal after a malicious break-in by an outside user. Should your superuser account be compromised, the offending party will have COMPLETE control over your portal instance and all the sites and user information that are contained therein.
So, as a rule of thumb and to sum this all up:
- Change the default "admin" and "host" usernames.
- Only login to your portal using the host/superuser account if you specifically need to access something in the Host Menu.
- Periodically change your password. A good practice is at least once every two months, but the more frequent, the better.
- Periodically check the Log Viewer in the Admin Menu to see if there are suspicious attempts at logging in to the web site. (Filter the log by "Login Failure" or "Login - superuser" types for easier reading.)
Happy coding!Labels: DotNetNuke
posted by The Mighty Will @
permalink
Wednesday, July 05, 2006
|
My daughter Paige has come to visit. Here is a family photo of all of us! Pictured (from left to right): Kohen, Kimbereley, Me, Paige, KariannLabels: Family Stuff
posted by The Mighty Will @
permalink
Migrating Development Software from .Net 1.0 to 2.0
|
ARGH!!! I have been having the worst time trying to install Microsoft SQL Server 2005 on my development machine at home. Since I had already been burned in the BETA initiation when I installed at work, I already knew to uninstall any .Net 2.0 development software before I began installation (BETA or not).
This time I was met with a HUGE surprise though. Although I had uninstalled everything that Microsoft's web site told us all to, the install of SQL Server 2005 kept telling me otherwise. Even their BETA uninstall tool was not functioning. The newest version would not complete the uninstall due to an XML error, and the one I downloaded with the BETA software many moons ago would just not complete the uninstall, thinking that I was not logged on as an Administrator. Microsoft really screwed us on this one! There should have been a much easier upgrade path from the BETA versions to the release versions of Visual Studio 2005 and SQL Server 2005.
I even went through the hassle of uninstalling my latest MDAC as one forum suggested. Ugh!
After much Googling, I finally found the answer here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
For some reason, Windows sometimes keeps Windows Installation information intact even when you uninstall software. I am using Windows 2000, so I am not sure if this would also be the case with XP. My development machine at work is XP and had a similar problem, but I did not need this tool to sort it out. The link above leads you to the tool that fixes the install information problem. However, be careful with it. It can mess you up if you are not paying attention.
This is a valuable piece of trial and error that I hope gets you out of hot water! :) Enjoy!
posted by The Mighty Will @
permalink
|
