System Administrator Documents

Introduction Needs of cloud computing Architectures INTRODUCTION Cloud computing provides us a means by which we can access the applications as utilities over the Internet. It allows us to create, configure and customize application online. With Cloud, Computing users can access database resources via the internet from anywhere for as long as they need without worrying about any maintenance or management of actual resources. What is Cloud Computing? Cloud Computing is a general term used to describe a new class of network-based computing that takes place over the Internet, Cloud can provide service over network, on public networks or on private networks, WAN, LAN or VPN. These platforms hide the complexity and details of the underlying infrastructure from users and applications by providing a very simple graphical interface or API (Applications Programming Interface). In addition, the platform provides on-demand services, which are a

Run PowerShell Scripts from Task Scheduler 1. Open Task Scheduler Open Task Scheduler and Create a new task. Name it and set your security options. 2. Set Triggers Click on the Triggers tab and set your schedule or event that will trigger the running of your Powershell script. 3. Create your Action Click on the Actions tab and click on New. Action: Start a program Program/script: Powershell.exe You don't need to put a path as it should already be on your system. 4. Set Argument First, you need to set the ExecutionPolicy. You have two options here, you can set the ExecutionPolicy on the machine or you can do it on a per-script basis. Read the PowerShell ExecutionPolicy link below as it talks about or you can issue the command: Get-Help About_execution_policies To set the execution policy globally, you can issue this command from within PowerShell: Set-ExecutionPolicy Unrestricted Or use one of the other settings avai

DOS Command to bind  HTTPS domain  in IIS . ->: Bind with all assigned ip. appcmd set site /site.name:"Site name in  iis" /+bindings.[protocol='https',bindingInformation='*:443:Domain Header name'] ->: Bind with Assigned IP. appcmd set site /site.name:" Site name in  iis" /+bindings.[protocol='https',bindingInformation='10.0.0.199:443:Domain Header name']

Switching between Drush major versions As I do a lot of work on legacy code and sites, I find it useful to have multiple versions of  Drush  installed on my laptop; it's also handy for testing version compatibility of my own projects like  Drush Instance . However, for convenience, I also want to be able to refer to any given Drush version as just "drush" at the command prompt. If you want to do this, you need local installations of more than one Drush versions, in different locations; and a switching mechanism. Here's one possible solution, for Debian/Ubuntu. Installing Drush versions in /opt My personal preference for manual installations is in. /opt I believe this can cause problems on some OSX versions at least, so if you've got some peculiarity with your own system then do feel free to install these packages where you see fit. To begin, create if /opt it doesn't already exist, and make it owned by you. sudo mkdir / opt sudo chown MY-U