Server Core installation option | Minimal Server Interface | Server with a GUI installation option | Desktop Experience feature installed | |
---|---|---|---|---|
Command prompt | available | available | available | available |
Windows PowerShell/Microsoft .NET | available | available | available | available |
Server Manager | not available | available | available | available |
Microsoft Management Console | not available | available | available | available |
Control Panel | not available | not available | available | available |
Control Panel applets | not available | some available | available | available |
Windows Explorer | not available | not available | available | available |
Taskbar | not available | not available | available | available |
Notification area | not available | not available | available | available |
Internet Explorer | not available | not available | available | available |
Built-in help system | not available | not available | available | available |
Themes | not available | not available | not available | available |
Windows 8 Shell | not available | not available | not available | available |
Windows Store and support for Windows Store apps | not available | not available | not available | available |
Windows Media Player | not available | not available | not available | available |
วันอาทิตย์ที่ 28 ธันวาคม พ.ศ. 2557
This table summarizes which features are available locally depending on which installation option you choose.
วันจันทร์ที่ 22 ธันวาคม พ.ศ. 2557
Top 10: Windows Firewall Netsh Commands
Everyone has probably heard that Windows Server 2012 will add around 2,300 new Windows PowerShell commands. Today, however, PowerShell still works with just a subset of the Windows Server management functions. One area that it doesn't directly touch is the ability to configure Windows Server networking and firewall functions, for which you need to use the venerable netsh commands. Even with the advent of PowerShell, netsh has continued to evolve, and it's particularly useful for configuring Windows Server Core.
Related: Network Configuration Tasks with Netsh
In this column, I'll show you 10 handy netsh commands you can use to query and configure your Windows Firewall settings. It's worth noting that you can call these netsh commands from within your PowerShell scripts.
10. Query firewall rules: One of the first things you'll probably need to use netsh for is to discover Windows Firewall's current configuration properties. You can query Windows Firewall settings using the following netsh command:
9. Enable and disable Windows Firewall: It's typically a best practice to leave Windows Firewall enabled, but sometimes when you're performing testing or setting up new applications, you need to turn Windows Firewall off for a period. The following commands illustrate how to turn Windows Firewall off and then back on:
8. Reset Windows Firewall: If you make a mistake configuring Windows Firewall, you might want to use the following netsh command to reset it back to its default settings:
7. Set logging: The default path for the Windows Firewall log files is \Windows\system32\LogFiles\Firewall\pfirewall.log. The netsh command below changes the location of the log file to the C:\temp directory:
6. Allow and prevent ping: You can use netsh to control how and if a given system responds to ping requests. The following two netsh commands show how you can block and then open Windows Firewall to ping requests:
5. Enable and delete a port: One of the most common things you need to do with Windows Firewall is open ports that are used by different programs. The following examples show how to use netsh to create a rule to open and then close port 1433, which is used by Microsoft SQL Server:
4. Enable a program: Another common task is opening Windows Firewall for a given program. The following example illustrates how to add a rule that enables Windows Live Messenger to work through Windows Firewall:
3. Enable remote management: Another common requirement, especially when you're setting up new systems, is to enable remote management so that tools such as the Microsoft Management Console can connect to remote systems. To open Windows Firewall for remote management, you can use the following command:
2. Enable Remote Desktop Connection: One of the first things I do with most of the server systems I set up is enable Remote Desktop Connection for easy remote systems management. The following command shows how to use netsh to open Windows Firewall for Remote Desktop Connections:
1. Export and import firewall settings: After you get Windows Firewall configured, it's a good idea to export your settings so that you can easily reapply them later or import them into another system. In the following netsh commands, you can see how to export and then import your Windows Firewall configuration:
Learn more: Netsh Command Syntax for the Netsh Firewall Context
Configure Windows Server networking and firewall functions from the command line
Advertisement
Related: Network Configuration Tasks with Netsh
In this column, I'll show you 10 handy netsh commands you can use to query and configure your Windows Firewall settings. It's worth noting that you can call these netsh commands from within your PowerShell scripts.
10. Query firewall rules: One of the first things you'll probably need to use netsh for is to discover Windows Firewall's current configuration properties. You can query Windows Firewall settings using the following netsh command:
netsh advfirewall firewall show rule name=all
netsh advfirewall set allprofiles state on
netsh advfirewall set allprofiles state off
netsh advfirewall set allprofiles state off
netsh advfirewall reset
netsh advfirewall set currentprofile logging filename "C:\temp\pfirewall.log"
netsh advfirewall firewall add rule name="All ICMP V4" dir=in action=block protocol=icmpv4
netsh advfirewall firewall add rule name="All ICMP V4" dir=in action=allow protocol=icmpv4
netsh advfirewall firewall add rule name="All ICMP V4" dir=in action=allow protocol=icmpv4
netsh advfirewall firewall add rule name="Open SQL Server Port 1433" dir=in action=allow protocol=TCP localport=1433
netsh advfirewall firewall delete rule name="Open SQL Server Port 1433" protocol=tcp localport=1433
netsh advfirewall firewall delete rule name="Open SQL Server Port 1433" protocol=tcp localport=1433
netsh advfirewall firewall add rule name="Allow Messenger" dir=in action=allow program="C:\programfiles\messenger\msnmsgr.exe"
netsh advfirewall firewall set rule group="remote administration" new enable=yes
netsh advfirewall firewall set rule group="remote desktop" new enable=Yes
netsh advfirewall export "C:\temp\WFconfiguration.wfw"
netsh advfirewall import "C:\temp\WFconfiguration.wfw"
netsh advfirewall import "C:\temp\WFconfiguration.wfw"
Distributed Transaction Coordinator
netsh advfirewall firewall add rule name="MSDTC" dir=in action=allow program="%windir%\system32\msdtc.exe" enable=yes
netsh advfirewall firewall add rule name="Distributed Transaction Coordinator" dir=in action=allow program="%windir%\system32\msdtc.exe" enable=yes
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (TCP-In)" new enable=yes profile="domain"
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (TCP-Out)" new enable=yes profile="domain"
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (RPC)" new enable=yes profile="domain"
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (RPC-EPMAP)" new enable=yes profile="domain"
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (TCP-In)" new enable=yes profile="domain"
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (TCP-Out)" new enable=yes profile="domain"
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (RPC)" new enable=yes profile="domain"
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (RPC-EPMAP)" new enable=yes profile="domain
netsh advfirewall firewall set rule group="Distributed Transaction Coordinator" new enable=yes
netsh advfirewall firewall set rule group="File and Printer Sharing" new enable=yes
To begin, open a command prompt as administrator.
To turn off Windows Firewall for Domain Networks type the following command:
netsh advfirewall set domain state off
To turn off Windows Firewall for Private Networks type the following command:
netsh advfirewall set private state off
To turn off Windows Firewall for Public Networks type the following command:
netsh advfirewall set public state off
To turn off Windows Firewall for All Networks (Domain, Private, Public) type the following command:
netsh advfirewall set allprofiles state off
Now, if you needed to turn Windows Firewall back on using this utility you can type the same commands and just change “off” to “on”. For example, if you wanted to turn the Windows Firewall on for all networks you would type the following command:
netsh advfirewall set allprofiles state on
netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = SUBNET profile = CURRENT
netsh advfirewall firewall add rule name="MSDTC" dir=in action=allow program="%windir%\system32\msdtc.exe" enable=yes
netsh advfirewall firewall add rule name="Distributed Transaction Coordinator" dir=in action=allow program="%windir%\system32\msdtc.exe" enable=yes
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (TCP-In)" new enable=yes profile="domain"
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (TCP-Out)" new enable=yes profile="domain"
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (RPC)" new enable=yes profile="domain"
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (RPC-EPMAP)" new enable=yes profile="domain"
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (TCP-In)" new enable=yes profile="domain"
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (TCP-Out)" new enable=yes profile="domain"
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (RPC)" new enable=yes profile="domain"
netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (RPC-EPMAP)" new enable=yes profile="domain
netsh advfirewall firewall set rule group="Distributed Transaction Coordinator" new enable=yes
netsh advfirewall firewall set rule group="File and Printer Sharing" new enable=yes
To begin, open a command prompt as administrator.
To turn off Windows Firewall for Domain Networks type the following command:
netsh advfirewall set domain state off
To turn off Windows Firewall for Private Networks type the following command:
netsh advfirewall set private state off
To turn off Windows Firewall for Public Networks type the following command:
netsh advfirewall set public state off
To turn off Windows Firewall for All Networks (Domain, Private, Public) type the following command:
netsh advfirewall set allprofiles state off
Now, if you needed to turn Windows Firewall back on using this utility you can type the same commands and just change “off” to “on”. For example, if you wanted to turn the Windows Firewall on for all networks you would type the following command:
netsh advfirewall set allprofiles state on
netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = SUBNET profile = CURRENT
วันพฤหัสบดีที่ 27 พฤศจิกายน พ.ศ. 2557
Remove registry entries for a corrupt Windows 7 roaming profile
Remove registry entries for a corrupt Windows 7 roaming profile
log onto the computer as a local administrator.
open the registry by typing regedit in the start window.
locate the following registry key path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileList
Find the profileimagepath containing the user you wish to delete and delete the entire key
log off the computer as admin and back on as the user you are trying to fix. Log off immediately and then log back on again in order to create the profile and syncronise the profile properly.
http://nzcommunityschools.wordpress.com/how-tos-for-your-computer/how-to-reset-a-windows-7-roaming-profile/remove-registry-entries-for-a-corrupt-windows-7-roaming-profile/
*Remove registry entries for a corrupt Windows 7 roaming profile
In the case where you have deleted the user account from the local computer without using the advanced profiles setting, you will need to remove the registry entries for the user account before logging back on. This must be done by an administrator. A visual sign that this needs to be done can be the message that you have been logged on with a tempoary profile each time you log on.
log onto the computer as a local administrator.
open the registry by typing regedit in the start window.
locate the following registry key path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileList
Find the profileimagepath containing the user you wish to delete and delete the entire key
log off the computer as admin and back on as the user you are trying to fix. Log off immediately and then log back on again in order to create the profile and syncronise the profile properly.
http://nzcommunityschools.wordpress.com/how-tos-for-your-computer/how-to-reset-a-windows-7-roaming-profile/remove-registry-entries-for-a-corrupt-windows-7-roaming-profile/
วันอังคารที่ 11 พฤศจิกายน พ.ศ. 2557
Using sysprep without removing drivers
Using sysprep without removing drivers:
How to use sysprep without removing drivers:
Configure your answer file to persist the drivers by specifying the
PersistAllDeviceInstalls setting in the Microsoft-Windows-PnPSysprep.
true
Another way would be to configure the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Settings\sppnp set PersistAllDeviceInstalls to 1.
Configure your answer file to persist the drivers by specifying the PersistAllDeviceInstalls setting in the Microsoft-Windows-PnPSysprep.
<settings pass="generalize">
<component name="Microsoft-Windows-PnpSysprep">
<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
</component>
Another way would be to configure the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Settings\sppnp set PersistAllDeviceInstalls to 1.
sysprep.exe /generalize /unattend:answerfile
http://www.youtube.com/watch?v=PWnPWoQ1jqI
วันอังคารที่ 28 ตุลาคม พ.ศ. 2557
Unable to Delete Replication Partners within SEP Manager
Hello,
Change the MSL for all groups at the primary server to the default MSL of the primary.
Follow the Process as shown below:
NOTE: Make sure you Assign the Default Policy to all the Groups and Sub-groups.
HOPE THAT WORKS FOR YOU.
Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3
http://www.symantec.com/connect/forums/unable-delete-replication-partners-within-sep-manager
วันอาทิตย์ที่ 26 ตุลาคม พ.ศ. 2557
On MSDTC.reg
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC]
"AllowOnlySecureRpcCalls"=dword:00000000
"TurnOffRpcSecurity"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\Security]
"AccountName"="NT AUTHORITY\\NetworkService"
"DomainControllerState"=dword:00000000
"LuTransactions"=dword:00000001
"NetworkDtcAccess"=dword:00000001
"NetworkDtcAccessAdmin"=dword:00000001
"NetworkDtcAccessClients"=dword:00000001
"NetworkDtcAccessInbound"=dword:00000001
"NetworkDtcAccessOutbound"=dword:00000001
"NetworkDtcAccessTip"=dword:00000000
"NetworkDtcAccessTransactions"=dword:00000001
"XaTransactions"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\Security\XAKeyCNGKeyDataBlob]
"6c6efbe0-9741-411c-9eeb-8fd15f815e78"=hex:4b,44,42,4d,01,00,00,00,10,00,00,00,\
c1,f8,62,5f,f1,b8,d9,47,b3,e7,6b,0d,c8,39,84,ed
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC]
"AllowOnlySecureRpcCalls"=dword:00000000
"TurnOffRpcSecurity"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\Security]
"AccountName"="NT AUTHORITY\\NetworkService"
"DomainControllerState"=dword:00000000
"LuTransactions"=dword:00000001
"NetworkDtcAccess"=dword:00000001
"NetworkDtcAccessAdmin"=dword:00000001
"NetworkDtcAccessClients"=dword:00000001
"NetworkDtcAccessInbound"=dword:00000001
"NetworkDtcAccessOutbound"=dword:00000001
"NetworkDtcAccessTip"=dword:00000000
"NetworkDtcAccessTransactions"=dword:00000001
"XaTransactions"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\Security\XAKeyCNGKeyDataBlob]
"6c6efbe0-9741-411c-9eeb-8fd15f815e78"=hex:4b,44,42,4d,01,00,00,00,10,00,00,00,\
c1,f8,62,5f,f1,b8,d9,47,b3,e7,6b,0d,c8,39,84,ed
วันเสาร์ที่ 25 ตุลาคม พ.ศ. 2557
Autounattend.xml
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>0409:00000409</InputLocale>
<UserLocale>th-TH</UserLocale>
<UILanguage>en-US</UILanguage>
<SystemLocale>th-TH</SystemLocale>
</component>
<component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<UserData>
<ProductKey>
<Key>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</Key>
<WillShowUI>OnError</WillShowUI>
</ProductKey>
<Organization>Praram9 Hospital Co.,Ltd.</Organization>
<FullName>IT</FullName>
<AcceptEula>true</AcceptEula>
</UserData>
<ImageInstall>
<OSImage>
<InstallFrom>
<MetaData wcm:action="add">
<Key>/IMAGE/NAME</Key>
<Value>Windows 7 PROFESSIONAL</Value>
</MetaData>
</InstallFrom>
<InstallToAvailablePartition>false</InstallToAvailablePartition>
<WillShowUI>OnError</WillShowUI>
</OSImage>
</ImageInstall>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<AutoLogon>
<Password>
<Value>xxxxxx</Value>
</Password>
<Enabled>true</Enabled>
<LogonCount>5</LogonCount>
<Username>Administrator</Username>
</AutoLogon>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>2</ProtectYourPC>
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>false</SkipUserOOBE>
</OOBE>
<UserAccounts>
<AdministratorPassword>
<Value>xxxxxx</Value>
</AdministratorPassword>
</UserAccounts>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>Praram9-PC</ComputerName>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:H:/Win7.1x86/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
25-10-2557
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>0409:00000409</InputLocale>
<UserLocale>th-TH</UserLocale>
<UILanguage>en-US</UILanguage>
<SystemLocale>th-TH</SystemLocale>
</component>
<component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<UserData>
<ProductKey>
<Key>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</Key>
<WillShowUI>OnError</WillShowUI>
</ProductKey>
<Organization>Praram9 Hospital Co.,Ltd.</Organization>
<FullName>IT</FullName>
<AcceptEula>true</AcceptEula>
</UserData>
<ImageInstall>
<OSImage>
<InstallFrom>
<MetaData wcm:action="add">
<Key>/IMAGE/NAME</Key>
<Value>Windows 7 PROFESSIONAL</Value>
</MetaData>
</InstallFrom>
<InstallToAvailablePartition>false</InstallToAvailablePartition>
<WillShowUI>OnError</WillShowUI>
</OSImage>
</ImageInstall>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<AutoLogon>
<Password>
<Value>xxxxxx</Value>
</Password>
<Enabled>true</Enabled>
<LogonCount>5</LogonCount>
<Username>Administrator</Username>
</AutoLogon>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>2</ProtectYourPC>
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>false</SkipUserOOBE>
</OOBE>
<UserAccounts>
<AdministratorPassword>
<Value>xxxxxx</Value>
</AdministratorPassword>
</UserAccounts>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>Praram9-PC</ComputerName>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:H:/Win7.1x86/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
25-10-2557
สมัครสมาชิก:
บทความ (Atom)