Hewlett Packard Proliant DL320e G8 Server Quickspecs. Memory One of the following depending on Model Type HP SmartMemory. Unbuffered (UDIMM). The HP ProLiant DL380p Gen8 sets the next generation standards of 2U 2-socket rack servers for the industry. With enhanced configuration flexibility. HPE Training calendar for locating courses and course offerings. Page features selection by region, course type, language, technology and training mode with links to. At VMworld 2014 VMware revealed bits and pieces of what’s new in vSphere 6.0. A lot of information was still under NDA and not disclosed, so attendees didn’t get. View and Download HP ProLiant DL360 Generation 7 (G7) quickspecs online. ProLiant DL360 Generation 7 (G7) Server pdf manual download. Welcome to Microsoft TechEd 2013 live blogging! I started off the conference by attending the all-day Microsoft System Center Configuration Manager 2012 SP1 session. The Converged Infrastructure information library is a search based tool used to access user guides, technical documentation, and other collateral for a variety of. Converged Infrastructure Information Library | Hewlett Packard Enterprise. HP Data Protector Best Practice Guide Enu - Download as PDF File (.pdf), Text File (.txt) or read online. HP Data Protector Best Practice Guide Enu.Tech. Ed 2. 01. 3: Configuration Manager 2. SP1 Lessons Learned. Welcome to Microsoft Tech. Ed 2. 01. 3 live blogging! I started off the conference by attending the all- day Microsoft System Center Configuration Manager 2. SP1 session. Since this was a pre- con, it ran all day so a TON of content was presented. You can find tweets about this session at #TEPRC0. The speakers were Kent Agerlund and Johan Arwidmark. Both were excellent, and presented a lot of real- world deployment information and lessons learned. There were a few major take- aways that anyone looking at SCCM 2. SP1 should understand: SQL server design and architecture is hugely critical. You can’t just do a click next install of SQL server and expect SCCM to perform within your expectations. You need to have a detailed understanding of SQL server best practices, including Temp. DB settings. It’s is also strongly recommended to combine SQL server and your primary site roles onto a single server/VM, unless you are a huge organization (sizing details are below). Yes, let me state that again, don’t use a remote SQL instance that is hosting other databases. Use a dedicated local SQL server instance for SCCM. Once SQL server is installed, it needs regular maintenance to keep it performing well. Backups, re- indexing, and other jobs must be run regularly or performance can tank. Session notes have a lot more details and links to some free tools. If you are using SCCM 2. Yes, even for large multi- national companies with 1. K clients. Do NOT do multiple primary sites. Use MDT 2. 01. 2 SP1 to build all of your Windows golden images. The resulting WIM file can then be used by any deployment tool on the market, including SCCM or third- party tools. It will sequence and fully automate the injection of patches, software, and other tweaks. Do not build your OS images in SCCM, or you won’t be able to use them with other deployment solutions. The importance of creating intelligent collections cannot be understated. Read up on the SCCM 2. You will pay for the lack of planning down the road. Use a third- party program to scan for and patch non- MS updates, such as Java and Adobe products. Solarwinds or Secunia are the only two you should consider. A majority of vulnerablities are now in third- party products, not the MS OS. So if you aren’t properly patching third party software, you are just asking to get hacked. Session Notes. Configuration Manager 2. Goals: Empower Users. Unify Infrastructure. Simplify Administration – Most can consolidate to a single primary site. System Requirements. WS2. 00. 8 x. 64 or later (strongly recommend WS2. At least 1. 6- 2. GB RAM for primary site with SQL local. GB is more typical. GB RAM for secondary site. Dedicated disk arrays (Disk IO is HUGE. Poor performance is likely due to storage being slow). Typical disk layout: C: OS, D: Program, E: content library, F: DB files (1. GB), G: Temp. DB (5. GB), H DB Logs (5. GB). NTFS allocation size 6. KB for SQL volumes. SQL Guidelines: Recommend LOCAL SQL install on SCCM server (STRONG RECOMMENDATION!!!! Strongly Microsoft recommended.)Minimum SQL versions: SQL server 2. SP2 CU9, 2. 00. 8 R2 SP1 and CU6, 2. CU3, 2. 01. 2 SP1. SQL 2. 01. 2 Always On is NOT supported. Don’t use SQL mirroring (may appear to work, but SP upgrades will break)Pre- create the SQL database so you can control the layout. Don’t let SCCM create it, as performance will not be good. Estimate 3- 5. MB per client for database storage. Not a traditional SQL database. Very high SQL load from constant queries from all clients. Site server 1: DB – Site System; Server 2 – DP/SUP/MPDo NOT combine databases from other system center products. Don’t build a giant SQL cluster for all system center products. MUST carefully consider Temp. DB. 1 file per core, with no more than 8 files. Temp. DB file per v. CPU for VMs. Need to manually configure SQL memory usage so OS/SCCM has memory to use. Don’t leave to the default of infinite. Cap SQL log file size in SQL manager to what you think is the max. Turn off auto- growth. Don’t use full recovery model for Reporting Services database. Use simple for Reporting services. VM snapshots are NOT backups. Use SQL server backup feature. Uses compression for much smaller backups. Site Sizing: Less than 2. VM (including SQL)Less than 2. Server #1: SQLDB, primary site, SMS provider, endpoint protection, #2: MP, Software Update, DP, app catalog. K clients: #1: SQL DB, primary site, SMS, endpoint; #2- 4: MP, software update, DP, app catalog. Hydration Kit for Config. Mgr 2. 01. 2 SP1 is here: Automates provisioning AD, SCCM deployment via scripts. If using Hyper- V don’t use dynamic memory for the VM during deployment. You can configure it to use dynamic memory after. Can create a huge bootable ISO and it automates the installation following best practices. Great for creating labs, then deploying in production exactly like the lab. Works on Hyper- V, VMware and physical servers. Other good tools located at: Deployment. Research and Deploymentbunny. IMPORTANT: Site maintenance tasks: Rebuild Indexes (always enable it; runs every 7 days). Use a third- party solution as the build- in job is NOT reliable. Use the DB maintennace script from Ola. Just enter the site code, and use on WSUS database as well. This is a MUST HAVE. USE THE SCRIPT. Microsoft internally uses this script, so you should too. Strongly recommend only a single primary site. For secondary sites, consider them when you have 5. Migrating from Config. Mgr 2. 00. 7 SP1. Don’t need to configure boundary sites since you should only have one primary site. Co- existence is perfectly acceptable. Don’t do a big bang migration. SCCM 2. 01. 2 can pull config data from 2. SP1, so they are sync’d. DP migration can take many hours or even a week, if you have huge amount of content. Migrating collections: Consider security, folders, users & devices. Limit collections. Create a base collection, then use include/exclude to customize the rules. Decide on role based access controls. Configure collection refresh cycle after migration. Limit use of folders – They are evil as you cannot assign permissions. Good folder name is “Software Updates”. Setup role based administration in 2. Software Distribution. Software and OS packages are so big these days, you should use DPs at branch offices. Use WS2. 01. 2 for DP points. DPs are usually long lived, so start with the new OS. Create Power. Shell automation features. You can inject software updates/patches into Win. Win. 8 images. You can now pre- provision Bit. Locker with SCCM 2. SP1, so it starts encryption prior to OS deployment. Make sure server firmware is up to date, since Win. PE 4. 0 won’t boot on servers with older firmware. PXE performance is creaming on WS2. Can boot a WS2. 01. WDS image in 4 seconds via PXE. Strongly urge users to add MDT 2. SP1 to SCCM OS deployment. Use Lite Touch mode to create master images. Use Zero Touch for added features – 2. MTD 2. 01. 2 SP1 add- on (free)Dynamic deployments are a HUGE value- add. Can customize OS deployments based on various parameters. New hardware uses UEFI so you need to boot into Win. PE 4. 0. Boot off memory sticks using FAT3. NTFS, for UEFI support. OSD deployment supports new App model. You can set primary user of a machine prior to deployment, so its customized for that user. User device affinity in CM2. New to CM2. 01. 2 SP1: WS2. Win. 8 OS deployment. Use MDT 2. 01. 2 Update 1 Lite Touch to create a reference image. Creates images that works with anything. Don’t create your image in SCCM. Image will be compatible with any other deployment solution you have when using MDT 2. It’s also 2x faster creating an image. You can copy the admin default profile, easy to delegate, and you can suspend deployment if needed. Take a look at the MDT Database admin tool here. MDT needs a separate WSUS instance (not the one you use for Conig. Mgr) for update approval“Request State Store” task must be added if you want to perform a machine backup. You can use WMI queries to insert specific drivers instead of relying on Pn. PNever share an application between OSD and CM deployment. Create an OSD security role, and limit the permissions to the OSD pacakges to the OSD team. Look at iconarchive. Software Update Management. Vulnerabilty intelligence + vulnerability scanning + patch creation + patch deployment. Define the update process: pilots, servers with auto restart, servers with manual restart, logically grouped servers, workstations in prod, excluded devices. Can use MS SC Orchestrator to orchestrate SCCM patching. Define your SLAs, collection design is #1 (HUGE!!), maintenance windows. Create a custom report (computer uptime in days). Can color code uptimes to see most recent reboots. Cortech Update Manager freebie tool. Don’t organize software updates by OS. Control everything through maintenance windows. Run a regulary query for expired updates and remove them from ALL deployments. Remember to still do the WSUS DB cleanup and re- index on a regular database. Solarwinds patch manager and Secunia are the only two you should consider using. Excellent third party support.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
September 2016
Categories |