Transparent Data Encryption (TDE) encrypts SQL Server, Azure SQL Database, and Azure SQL Data Warehouse data files, known as encrypting data at rest. You can take several precautions to help secure the database such as designing a secure system, encrypting confidential assets, and building a firewall around the database servers. However, in a scenario where the physical media (such as drives or backup tapes) are stolen, a malicious party can just restore or attach the database and browse the data. One solution is to encrypt the sensitive data in the database and protect the keys that are used to encrypt the data with a certificate. This prevents anyone without the keys from using the data, but this kind of protection must be planned in advance.
- Hits: 7794
In case if you need to remotely restart Windows service, here is my Powershell script.
As soon as we have ICMP/ping disabled between our development environments, I've used WMI pings to determine, if remote machine is running.
- Hits: 7779
In case if you ever need to create Windows service from an executable or even bat-file, please feel free to use the following configuration in Powershell DSC.
The solution based on the NSSM software which is very similar to srvany.exe (from Windows 2003 Kit). The main difference NSSM from srvany - is that srvany does not close the underlying process if the service is stopped. And NSSM does close it. Download NSSM.
- Hits: 6530
If you ever need to unzip BIG archive files in Powershell DSC configurations (during deployment some software), you will possibly get stuck, because using Archive resource is not suitable for this task as it is very slow. xArchive also will not help.
One possible solution is to unzip it with 7zip or some other command line utility using WindowsProcess resource, but be warned that WindowsProcess will just start the process and then will go to the next instruction in your configuration. See the example:
- Hits: 5824
Sometime it's very difficult to find error in Powershell script, especially if script is running in some dedicated session, for example, under SYSTEM account. There will be errors but you'll never know about them.
That's why I started to search a way to log output from Powershell-console to file. Here is the solution.
- Hits: 14946
Error "Get-PowerCLIVersion : The term 'Get-PowerCLIVersion' is not recognized as the name of a cmdlet, function, script file, or operable program." while starting VMware vSphere PowerCLI
Sometimes the following error appear while starting VMware vSphere PowerCLI:
Get-PowerCLIVersion : The term 'Get-PowerCLIVersion' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1:38 char:12 + $version = Get-PowerCLIVersion + ~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Get-PowerCLIVersion:String) , CommandNotFoundExce ption + FullyQualifiedErrorId : CommandNotFoundException
- Hits: 16889
More Articles …
- Search and\or delete messages in mailboxes in Exchange 2010/2013/2016
- Windows 7/2008/R2/8/8.1 continuously loading into Recovery Mode
- Tracking messages in Exchange 2013 log files - easy and quick!
- Mass import into MS SQL database script with Powershell
- Step-by-step deploying AlwaysOn on MS SQL 2012
- High availability and fault tolerance of Client Access Servers (CAS) in Exchange 2013
- Changing service account for MS SQL Server 2012 and the following issues
Page 3 of 14