changing the Windows 8 network location from public to private
Hit Winkey + R to open Run prompt and type gpedit.msc
Navigate to: Computer Configuration | Windows Settings | Security Setting | Network List Manager Policies
Choose your Network name from the right pane. In my case network name was Network 2
Go to Network Location tab and change the Location type from Not configured to Private.
I am trying to connect to a Microsoft SQL 2008 or another server which is not on port 1433. How do I indicate a different port number when connecting to the server using SQL Management Studio?
In SQL Server Configuration Manager. Go to Sql Native Client Configuration, Select Client Protocols, Right Click on TCP/IP and set your default port there.
to connect to sql, enter the server address and then enter the port number after the comma SQLSERVER\InstanceName,portnumber - SQL\InstSQL, 1025
sql server processes and find port
netstat -a -b
If you're talking about the All Users desktop, it can be found here:
- Windows Server 2003: %ALLUSERSPROFILE%\Desktop
- Windows Server 2008 and above: %PUBLlC%\Desktop
If want to remove shortcuts from each user's desktop, then you could write a script that deletes all *.LNK files from %USERPROFILE%\Desktop, or where ever their Desktop is redirected to ( %HOMESHARE%\Desktop).
Step 1. Edit a GPO that targets the computers that you want to apply the home page setting.
Step 2. Navigate to User Configuration > Preferences > Control Panel Settings > Windows Settings
Step 3. Click on the “Action” menu and click on “New” and then click on “Shortcut”
Step 4. Change the Action to “Delete” then select “All Users Desktop” and then type “Adobe Reader 9” in the name field.
The term 'test.ps1' 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.
When running a script like
./Test.ps1 the script is expected to be in the current working directory (
Depending on the environment from which you're executing that statement the working directory may not be what you expect, though.
Here are some commands that allow you to determine the current working directory when run the same way as your script:
$PWD.Path (Get-Location).Path (Resolve-Path '.').Path
There are basically 3 ways to deal with the issue:
- Specify the path to your PowerShell script relative to the current working directory.
Change the current working directory to the location of the PowerShell script:
Push-Location 'C:\temp\folder' .\Test.ps1 Pop-Location
Run the PowerShell script with its full path:
If the executable's filename, path, or pathname doesn't contain spaces, using the call (&) operator is optional. Otherwise, the call operator is required.