Surfing all over the net, I found a very handy powershell cheat sheet that was put together by Ben Pearce. Anyways, here’s the download link (just click on the picture).
Big hello to the guys from www.bug.hr
Surfing all over the net, I found a very handy powershell cheat sheet that was put together by Ben Pearce. Anyways, here’s the download link (just click on the picture).
Big hello to the guys from www.bug.hr
Hi, last couple of days I have setuped over 10 Windows 2008 servers for hosting services for testing or production, so I am pretty bored with repeating the same stuff all over again
, but, here’s a recorded video tutorial of one installation process. Because the video is pretty straightforward, I’ve decided that there is no need to explain every step of the installation.
Click on the HD button and put the video into full screen mode, so you can see all the details.
In the next post, I will show you how to install Microsoft SQL server 2008 Express .
Cheers!
No, I wont explain everything in this post. This post is just a annoucement, so you can know what will you read in a couple of next posts. We will cover the installation of IIS 7( Internet Information Services), MS SQL server, MYSQL server, PHP 5, Perl, Awstats and finally, integrating everything in DotNetPanel, the web hosting control panel for Windows Servers. I will not explain or show how to install the OS on the server, because its a rudimentary and boring stuff
, but being awesome, here’s a link to the video someone made
Tired of old point and click interface?
Powershell is the new purple in computer world
haha…Seriously!
So, here’s a little script that will add the Ip address you want to the existing firewall rule.
As you can see, it fairly simple, and there’s no need to explain it too much….
Function IP
{
param ($ipadress = $(Read-host "Enter IP address"))
$rule = "YOUR PREVIOUSLY CREATED RULE NAME"
Write-host "Adding address :" $ipadress -foregroundcolor "Red"
Start-sleep -s 5
netsh advfirewall firewall set rule name="$rule" new remoteip="$ipadress" action="allow"
}
IP
Only thing you have to do in the script is to enter your fireall rule name.
When you start the script, it will ask you to enter desired ip address, and press enter. After that, wait 5 seconds and thats it
Cheers!
How many time did you find yourself in a situation where you need a reliable, stable and strong server? How to even determine if your server is stable enough? How to know what kind of continous load can it handle? Will it crash if it gets under heavy load for a couple of hours? Well, today, I’ve found myself in a situation like that. I have installed HyperV on some server we have at the office and wanted to see how it will perfom under extreme heavy load and how stable everyhing was .
By extreme heavy load I assume about 200 concurent users clicking every 1-3 seconds on a random page that is being served on the server . When you look at the number of 200 concurrent users, you can say: ” Hey, 200 users isnt that big of a number for a server to handle” …and you would be absolutely right
… if the server i was trying to “kill” didnt have 1 cpu core and 1 gb of ram assigned to it
.
So..the point was to simulate real life conditions as much as possible. To do that, once more, I turned to Linux and the little piece of awesome software called “Siege”. You can download it here. The software is able to simulate almost real user like behavior on a web page. It can randomly open link in a specified interval, simulate 200+ users at the same time without any problems and so on.
To do some proper testing I’ve installed some php+mysql and asp.net+sql2008 applications to simulate a real-life scenario as much as possible. As we all know, one of pretty hungry applications for Linux is Joomla for the PHP+MYSQL combination and DotNetNuke for ASP.Net and MSSql combination. All cacheing techniques on the application and the IIS were turned off so we can maximize the load to the server.
The server is based on Windows 2008 Server R2 Standard Edition and SQL Express 2008 .
I’ve told Siege to simulate 100 users on the Joomla site and 100 users on the ASP.Net site for 24 hours. At this moment, tests are running for 6 hours and everything seems to be in perfect order. Here’s a couple of pictures
As we like to say it..BURN BABY BURN! About 16 more hours to go under 100% cpu
Results are coming soon…in about 20 hours
more or less ….