While working on SQL (see my previous post…) we of course got locked out…

I found a post that helped! (Thanks Google-fu!)

You can either run this query:

ALTER LOGIN sqluser WITH CHECK_POLICY = OFF;
ALTER LOGIN sqluser WITH CHECK_POLICY = ON;
GO

or via GUI, uncheck the box:

sqluser

 

PS: Dear Vendor, if you are selling a product, please know the ins and outs of the product AND the other products that are needed to get everything to work. Thank you.

Source:

http://www.sqldbadiaries.com/2010/07/21/unlock-sql-user-without-changing-the-password/#ixzz2OBIJCsqv

 


I was working with a vendor for some specialty software, they could install the software but were not able to configure SQL… though the software is heavily integrated with SQL.

I have to admit, I am not too familiar with SQL so troubleshooting it, I have to utilize my Google fu…

Error:

_“Error: Test connection to the database server has failed because of network problems:

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.”_

Fix:

  1. Login to the server -> Start -> All Programs -> Microsoft SQL Server -> Configuration Tools -> SQL Server Configuration Manager -> SQL Server Network Configuration -> Protocols for MSSQLSERVER -> right click “TCP/IP” and select “Enable”.

  2. Start -> Run -> type “services.msc” -> Restart SQL service.

PROTIP:

Also check a service called ‘SQL Server Browser‘ and make sure it is running…

 


I was today stuck in a 2003 VM for a while…. no intergration AGHr…. here some things that are REALLY helpful. :o)

Standard: CTRL + ALT + DEL 
VMC: CTRL + ALT + END 
Displays the Task Manager or Windows Security dialog box on Windows (or logs in).
Standard: ALT + TAB 
VMC: ALT + PAGE UP 
Switches between programs from left to right.
Standard: ALT + SHIFT + TAB 
VMC: ALT + PAGE DOWN 
Switches between programs from right to left.
Standard: ALT + ESC 
VMC: ALT + INSERT 
Cycles through the programs in the order they were started.
Standard: CTRL + ESC 
VMC: ALT + HOME 
Displays the Windows Start menu.
Standard: N/A 
VMC: CTRL + ALT + PAUSE 
Changes the Virtual Machine Connection window to / from full screen mode.
Standard: N/A 
VMC: CTRL + ALT + LEFT ARROW 
Releases mouse and keyboard focus from the Virtual Machine Connection window.

 

 


We have a Terminal Server and need to install Office without a Volume License.

According to THIS, that is allowed with E3 licensing.

o365

 

 

 

So, a couple of things to note here:

  1. RDS is not permitted for Small Business premium

  2. RDS IS permitted for M, E3 and E4

  3. There are no caveats or foot notes as there used to be

Now the actual question, HOW do you do it?

Here the answer:

1. Start by downloading the “Office Deployment Tool for Click-To-Run” and extract it in a shared directory.

  1. Navigate to your extracted folder (in our example \server\o365) and edit the ‘configuration.xml’ file following the Microsoft guidelines:
<Configuration>
<Add SourcePath="\\<path>\O365" OfficeClientEdition="32" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
<Updates Enabled="TRUE" />
<Display Level="Full" AcceptEULA="TRUE" />
<Property Name="SharedComputerLicensing" Value="1" />
</Configuration>
  1. Open CMD, navigate to the extraction folder (e.g. C:\O365) and run:
setup.exe /download \\server\O365\configuration.xml

Let it run it will download the installer, it will create a new folder called ‘Office’ and should be about 1GB once it finished.

  1. Run the installer from CMD
\\server\o365\setup.exe /configure \\server\o365\configure.xml

Once that is done you should have O365 installed and it can be activated with individual O365 (E3) licenses. :o)

 

 

 


We needed to change login scripts, or rather remove ’em as we replace ’em with GPOs. I exported the current scripts to a TXT and then just cleared the field in AD.

#  Load the AD module
Import-module ActiveDirectory 
#  Get all the AD user who have a login script and save it to a textfile
Get-ADUser -filter * -properties scriptpath | ft Name, scriptpath > C:\LogonScript.txt -Force
#  Clear the Logon script field in AD
Get-ADUser -Filter * -SearchBase "OU=TEST,DC=TEST,DC=local" | Set-ADUser -Clear scriptPath