All you need to do it put in the server name followed by sqlexpress
EG: sqlserversqlexpress and you can connect and manage it.
You will need to know a local password user such as SA for SQL authentication, or be logged into the server with a Windows administrator account that the same on both the management server and the SQLexpress server if you use Windows authentication.
I have been looking at the easiest way to get a LAMP server up and running in minutes.
I found the following command and it works like a charm!
sudo apt-get install lamp-server^ phpmyadmin
Follow the on screen prompts and you are good to go!
Type the following commands:
sudo vi /etc/hostname and change the name and save the file
sudo vi /etc/hosts and change the name and save the file
sudo service hostname start
then when you type hostname it should show the new name
*i – edit the file
*u – undo change you just made
:q – quit
:q! – quit without saving any changes
:wq – quit and write changes to file
Type the following command sudo nano /etc/network/interfaces
Find auto eth0 and edit the lines below.
If it is set for DHCP and you want to change it, change the following lines from:
iface eth0 inet dhcp
To something like this for example: (please use your own network IP addresses , DNS servers and domain name where applicable)
iface eth0 inet static
dns-nameservers 192.168.1.250 192.168.1.251
Open a CMD prompt and type the following
From the command line , type the following
SUDO dpkg-reconfigure tzdata
Follow the on screen prompts to set the time zone
I had done a backup and restore of my Samsung Galaxy S2 due to a hardware fault. When the phone booted back up it had “Problem Loading Widget Image” on the screen.
The way to fix this is to press on the widget for a few seconds, then drag it down to the trash can that will appear at the bottom of the screen
I wanted to modify a security group on some web servers that were behind an elastic load balancer so that they would only accept traffic from the load balancers. The problem was that I wasn’t sure what IP address or security group to allow. As the IP would change all of the time, you just need to allow this built-in group as the source for your port: amazon-elb/amazon-elb-sg.
This will just permit YOUR load balancers to reach your webservers on your chosen ports such as 80 and 443, and you will notice that it will be renamed in the amazon console to something like this amazon-elb/sg-x00xx000 (amazon-elb-sg) .
I had an issue where we built 6 Hyper-V Windows 2008 virtual machines with IIS that needed to connect to an SQL database that was on the Hyper-V host system.
We could not make the connection from the websites, nor could we ping or telnet to the Hyper-V host. The Hyper-V guests could ping and connect to any other system on the network, and the Hyper-V host could be connected to by any other system on the network.
The issue ended up being that we had used network teaming on the interfaces that hosted the virtual network for the Hyper-V guest operating systems. Hyper-V does not support network teaming, so we removed the network team, and the software and just used one of the physical network interfaces to create the Hyper-V virtual network.
Connectivity was restored after removing the network teaming configuration and then teaming software, and then rebooting the Hyper-V host server.