Buy 6 in 1 Surface Pro Hub Combo Adapter, VOASTEK USB 3.0 Hub with HDMI Adapter, LAN Port, Dual USB 3.0 Adapter and SD/TF/Micro SD Memory Card Reader Compatible Microsoft Surface 2017/Pro 4 |Unique Design with fast shipping and top-rated customer service. Newegg shopping upgraded ™. Search the world's information, including webpages, images, videos and more. Google has many special features to help you find exactly what you're looking for. 8ft 1/2 View 4-Light 1-Panel Plank The lower panel with plank detail combined with a 4-lite grille glass upper panel gives this 8 foot exterior fiberglass door a distinctly modern farmhouse look. Available with options for privacy or performance glass, divided lites and more; painted or stained, or primed and ready to paint. Visual Web Designer - Hazel Pro. Create beautiful, mobile-friendly websites and interactive web forms! - Responsive design editor makes it simple for anyone to build amazing websites without writing a single line of code - Supports modern web design elements including animation effects, interactive carousels, lightbox image galleries, video.
2200 - Home Designer Professional Overview
2207 - Becoming Familiar with the Interface
2209 - Zooming and Panning
2302 - Working with Multiple Windows and Tabbed Views
2211 - Becoming Familiar with the Library Browser
2303 - Working with Library Filters in Home Designer Pro
2304 - Using the Library Browser in Multiple Windows
2305 - Updating Existing Home Designer Library Content
2212 - Toolbar Customization
2306 - Working with Toolbars and Tool Buttons in Multiple Windows
2213 - Preferences
2214 - Default Settings
2216 - Templates: Creating Your Own
2217 - File Management
2218 - Cameras: 3D Views
2500 - Cameras - Camera View Options
2507 - Exporting and Viewing 360 Degree Panoramic Views
2223 - Display Options in Home Designer Pro
2502 - Copying Saved Cameras
2219 - Navigating in 3D
2307 - Creating Walkthroughs with Adjustable Key Frame Transitions
2308 - Side Clipping Section and Elevation Views
2221 - Saving and Restoring Camera Views
2309 - Creating New Backdrops for Camera Views
2224 - Exterior Walls
2311 - Constructing Different Wall Types
2225 - Dimension Defaults
2226 - Auto Exterior Dimensions
2312 - Automatic Interior Dimensions
2227 - Manual Dimensions
2228 - Dimensions in Home Designer Pro
2229 - Rooms and Interior Walls
2505 - Drawing Walls at Any Angle
2230 - Space Planning Assistant
2231 - Doors and Windows
2232 - Creating Multiple Level Floor Plans
Mail Designer Pro 2 6 13
2233 - Reference Display
2234 - Foundations and Basements
2235 - Walkout Basements
2236 - Daylight Basements
2314 - Foundation Cutouts for Garage Doors
2237 - Automatic Roofs
2238 - Roof Design in Home Designer Pro
2239 - Using the Gable Roof Line Tool
2240 - Drawing a Typical Dormer Condition
2242 - Home Designer Pro's Auto Dormer Tools
2243 - Auto Roof Returns and Variable Overhangs
2244 - Cathedral, Tray and Coffered Ceilings
2503 - Creating a Plant Shelf Ceiling
2245 - Custom Ceiling Planes
2246 - Stairs
Mail Designer Pro 2 6 1/2
2247 - Ramp Tools
2249 - Framing
2250 - Framing: Trusses
2315 - Framing Different Roof Sections with Different Rafter Spacing
2251 - Cabinets
2252 - Cabinets in Home Designer Pro
2313 - Dimensioning Cabinets in Elevation Views
2316 - Adding Appliances and Fixtures to Cabinets
2253 - Special Shaped Cabinets
2326 - Placing Cabinet Feet
2254 - Soffits
2255 - Using Custom Countertops
2327 - Creating Custom Backsplashes
2256 - Cabinet Moldings
2319 - Railings: Using Multiple Profiles & Materials for Railing Components
2257 - Finding and Using Library Objects
2259 - Window Treatments
2504 - Creating a Wall Niche
2260 - Applying a Picture to a Frame
2320 - Using the Object Eyedropper
2261 - Architectural Blocks
2262 - Importing 3D Symbols Principle 5 0.
2263 - Creating a Terrain Perimeter
2329 - Terrain Elevation Data, Retaining Walls and Modifiers
2330 - Terrain and Water Feature Tools
2265 - Importing Terrain Data From GPS or Text File
2331 - Terrain Walls, Curbs and Stepping Stones
2269 - Sprinkler Designer
2328 - Adding Garden Beds and Plants
2274 - Patios
2204 - Creating Decks
2276 - Deck Stairs
2275 - Deck Framing
2277 - Pools
2278 - Road and Sidewalk Tools
2280 - Importing a Home Photo to add Landscaping
2321 - Exporting High Definition Pictures and Transparent Backgrounds in Home Designer Pro
2281 - Adding Text
2282 - Callouts and Markers
2322 - Text Styles for Text and Labels
2323 - Text Styles in Home Designer Pro
2512 - Using Custom Watermarks
2283 - Creating and Editing CAD Objects
2324 - Using the Same Line Type Edit Handles
2284 - CAD in Cross Section and Elevation Views
2285 - Visual CAD Snaps
2511 - Using the Edit Area and Stretch CAD Tools
2286 - Electrical Tools
2288 - Wall Coverings
2289 - Applying Materials in 3D
2290 - Color Chooser
2291 - Custom Textures
2293 - Materials Lists
2294 - Printing Views
2295 - Printing in Home Designer Pro
2296 - Layouts
2287 - Moldings
2299 - Creating a Loft
2300 - Creating Angled Windows
2301 - Screen Porch - Quick Tip
10139 - Home Designer - Kitchen Design
10140 - Home Designer Quick Tip - Custom Beams
10138 - Home Designer - Quick Start
10141 - Home Designer - Beginning Roof Design
10142 - Home Designer Pro - Advanced Roof Design
10176 - Home Designer - Remodeling Project
10167 - Remodeling & Manual Roof Design
10143 - Home Designer – Bathroom Webinar
10144 - Home Designer - Landscape Design
11075 - Comparing Chief Architect to Home Designer Pro
-->Applies to: Configuration Manager (Current Branch)
When enabling TLS 1.2 for your Configuration Manager environment, start by ensuring the clients are capable and properly configured to use TLS 1.2 before enabling TLS 1.2 and disabling the older protocols on the site servers and remote site systems. There are three tasks for enabling TLS 1.2 on clients:
- Update Windows and WinHTTP
- Ensure that TLS 1.2 is enabled as a protocol for SChannel at the operating system level
- Update and configure the .NET Framework to support TLS 1.2
For more information about dependencies for specific Configuration Manager features and scenarios, see About enabling TLS 1.2.
Update Windows and WinHTTP
Windows 8.1, Windows Server 2012 R2, Windows 10, Windows Server 2016, and later versions of Windows natively support TLS 1.2 for client-server communications over WinHTTP.
Earlier versions of Windows, such as Windows 7 or Windows Server 2012, don't enable TLS 1.1 or TLS 1.2 by default for secure communications using WinHTTP. For these earlier versions of Windows, install Update 3140245 to enable the registry value below, which can be set to add TLS 1.1 and TLS 1.2 to the default secure protocols list for WinHTTP. With the patch installed, create the following registry values:
Important
Enable these settings on all clients running earlier versions of Windows before enabling TLS 1.2 and disabling the older protocols on the Configuration Manager servers. Otherwise, you can inadvertently orphan them.
Verify the value of the DefaultSecureProtocols
registry setting, for example:
If you change this value, restart the computer.
The example above shows the value of 0xAA0
for the WinHTTP DefaultSecureProtocols
setting. Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows lists the hexadecimal value for each protocol. By default in Windows, this value is 0x0A0
to enable SSL 3.0 and TLS 1.0 for WinHTTP. The above example keeps these defaults, and also enables TLS 1.1 and TLS 1.2 for WinHTTP. This configuration ensures that the change doesn't break any other application that might still rely on SSL 3.0 or TLS 1.0. You can use the value of 0xA00
to only enable TLS 1.1 and TLS 1.2. Configuration Manager supports the most secure protocol that Windows negotiates between both devices.
If you want to completely disable SSL 3.0 and TLS 1.0, use the SChannel disabled protocols setting in Windows. For more information, see Restrict the use of certain cryptographic algorithms and protocols in Schannel.dll.
Ensure that TLS 1.2 is enabled as a protocol for SChannel at the operating system level
TLS 1.2 is enabled by default. Therefore, no change to these keys is needed to enable it. You can make changes under Protocols
to disable TLS 1.0 and TLS 1.1 after you've followed the rest of the guidance in these articles and you've verified that the environment works when only TLS 1.2 enabled.
Verify the SecurityProvidersSCHANNELProtocols
registry subkey setting, as shown in Transport layer security (TLS) best practices with the .NET Framework.
Update and configure the .NET Framework to support TLS 1.2
Determine .NET version
First, determine the installed .NET versions. For more information, see Determine which versions and service pack levels of .NET Framework are installed.
Install .NET updates
Install the .NET updates so you can enable strong cryptography. Some versions of .NET Framework might require updates to enable strong cryptography. Use these guidelines:
NET Framework 4.6.2 and later supports TLS 1.1 and TLS 1.2. Confirm the registry settings, but no additional changes are required.
Note
Starting in version 2107, Configuration Manager requires Microsoft .NET Framework version 4.6.2 for site servers, specific site systems, clients, and the console. If possible in your environment, install the latest version of .NET version 4.8.
Update NET Framework 4.6 and earlier versions to support TLS 1.1 and TLS 1.2. For more information, see .NET Framework versions and dependencies.
If you're using .NET Framework 4.5.1 or 4.5.2 on Windows 8.1, Windows Server 2012 R2, or Windows Server 2012, it's highly recommended that you install the latest security updates for the .Net Framework 4.5.1 and 4.5.2 to ensure TLS 1.2 can be enabled properly.
For your reference, TLS 1.2 was first introduced into .Net Framework 4.5.1 and 4.5.2 with the following hotfix rollups:
- For Windows 8.1 and Server 2012 R2: Hotfix rollup 3099842
- For Windows Server 2012: Hotfix rollup 3099844
Configure for strong cryptography
Configure .NET Framework to support strong cryptography. Set the SchUseStrongCrypto
registry setting to DWORD:00000001
. This value disables the RC4 stream cipher and requires a restart. For more information about this setting, see Microsoft Security Advisory 296038.
Make sure to set the following registry keys on any computer that communicates across the network with a TLS 1.2-enabled system. For example, Configuration Manager clients, remote site system roles not installed on the site server, and the site server itself.
For 32-bit applications that are running on 32-bit OSs and for 64-bit applications that are running on 64-bit OSs, update the following subkey values:
For 32-bit applications that are running on 64-bit OSs, update the following subkey values:
Note
The SchUseStrongCrypto
setting allows .NET to use TLS 1.1 and TLS 1.2. The SystemDefaultTlsVersions
setting allows .NET to use the OS configuration. For more information, see TLS best practices with the .NET Framework.