Keith Smith - My Blog - Twitter @_KeithIT

Keith Smith - My Blog - Twitter @_KeithIT


Must have GPOs for Windows 10

Tuesday, September 27, 2016 - Posted by Keith A. Smith, in Microsoft

I started testing Windows 10 Enterprise in my environment. I know there are a number of new features in Windows 10 that aren't great for domains (PIN codes, Microsoft Accounts, etc.). After digging through all the GPO settings, I decided on the on the following. Once the modification was made and applied to the test machines, I brought in a few non-IT staff for UAT testing of the images. Everything went well, so I decided to share the settings I used in the GPO


  • lock Microsoft Accounts from being added or logging in (will not prevent accessing the Windows Store)
  • Force default lock screen and disable Spotlight
  • Disable WiFi Sense
  • Enable Virtualization Based Security with Secure Boot and DMA Protection only Credential Guard enabled with UEFI lock (NOTE: This will install the Hyper-V Hypervisor, with will cause VMware Workstation to stop working)
  • Disable first sign-in animation
  • Disable advertising ID
  • Configure telemetry to level 0 - Enterprise Only
  • Disable access to pre-release features
  • Disable feedback notifications
  • Disable access to insider builds
  • Disable Cortana
  • Disable Defender
  • Disable Windows Hello
  • Disable lock screen (the swipe up thing)
  • Disable 3rd party advertisements in Windows Spotlight
  • Disable picture and PIN password sign-in
And last but not least is setting explorer's default to This PC instead of Quick Access by doing the following:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced

Value Name: LaunchTo

Type: DWORD

Value: 1


-End
View Comments 0 Comments
Share Post   

Life and Work Balance

Monday, February 22, 2016 - Posted by Keith A. Smith, in Journal of thoughts

This Post is private, you need to be a active susbcriber to vew this Post. Click here to Subscribe
View Comments 0 Comments
Share Post   

vSphere 6.0 vCenter Windows 2012 R2 with SQL Server Install Guide

Tuesday, September 29, 2015 - Posted by Keith A. Smith, in VMware, Microsoft

VMware vSphere 6.0 has brought a simplified deployment model where the dependency on Microsoft SQL server has been reduced. You now have the option of using the built-in vPostgre SQL provided by VMware, vPostgres on windows is limited to 20 hosts and 200 virtual machines.

vCenter System requirements


Supported Windows Operation System for vCenter 6.0 Installation:

  • Microsoft Windows Server 2008 SP2 64-bit
  • Microsoft Windows Server 2008 R2 64-bit
  • Microsoft Windows Server 2008 R2 SP1 64-bit
  • Microsoft Windows Server 2012 64-bit
  • Microsoft Windows Server 2012 R2 64-bit

Supported Databases for vCenter 6.0 Installation:

  • Microsoft SQL Server 2008 R2 SP1
  • Microsoft SQL Server 2008 R2 SP2
  • Microsoft SQL Server 2012
  • Microsoft SQL Server 2012 SP1
  • Microsoft SQL Server 2014
  • Oracle 11g R2 11.2.0.4
  • Oracle 12c

1. Make sure that you using static IP for your VM and you create forward and reverse DNS records on your DNS server. Also make sure that the machine is part of Windows domain.

2. Create an account in your Active Directory, this will be used on the SQL server for the vCenter database

3. Now you need to create a blank SQL database on an SQL server.

4. Once your blank database is created, you need to add the account you created in your Active Directory. Make sure to give it sysadmin for the server role.


Before you start the installer make sure your Windows Server VM is fully patched, otherwise you might get a prompt to patch the server. The two patches that are needed are below



5. During the vCenter installation process you might get a prompt asking to give the administrator’s account the right to Log On as a service on the server that run vCenter.  You need to grant the domain account you created earlier the right to Log On as a service.

The steps:

  • Get to the Administrative Tools, and then double-click Local Security Policy.
  • In the console tree, double-click Local Policies, and then click User Rights Assignment.
  • In the details pane, double-click Log on as a service.


  • Click Add User or Group, and then add the domain account you created to the list of accounts that possess the Log on as a service right.


6. Important - The SQL server native client is necessary to create the system DSN. To download the SQL Server Native Client, click on the link below

This ODBC Driver for SQL Server supports x86 and x64 connections to SQL Azure Database, SQL Server 2012, SQL Server 2008 R2, SQL Server 2008, and SQL Server 2005.


http://www.microsoft.com/en-us/download/confirmation.aspx?id=36434



7. Now that the SQL Server Native Client is installed, create system DSN through ODBC data source administrator (64-bit).





Proceed through the wizard




8. Once you have fill out all the SQL server information, make sure you test the data source




If you everything is setup correctly then you should see this




9. Mount the vCenter server ISO and double click the autorun.exe


10. Proceed through the vCenter install




11. Once you get to the database settings, you will need to choose use an external database. If you DSN is blank then click the refresh button and it should appear




Continue the setup wizard and leave the default values… You should see the setup complete screen.  At this point you can open up a browser and visit the vCenter interface which uses adobe flash.


-End
View Comments 0 Comments
Share Post   

Apply BgInfo via Group Policy Logon Script

Monday, September 28, 2015 - Posted by Keith A. Smith, in Microsoft

BgInfo is a well known tool that allows having a background Wallpaper showing some information about your system. This will save time when the need arises to collect details or troubleshoot your systems.
To centrally apply BgInfo I recommend the use of a Group Policy Logon script. 

1. Prepare the Background Wallpaper to apply via BgInfo:
You need to:
• Copy the BgInfo.exe in a folder on \\yourdomain\netlogon
• Run BgInfo.exe, prepare the fields to display and then save your template in a .bgi file

2.   2.  Prepare a Logon Script to run BgInfo:

You can use the following script to run BgInfo:

reg add HKU\.DEFAULT\Software\Sysinternals\BGInfo /v EulaAccepted /t REG_DWORD /d 1 /f

\\yourdomain\netlogon\Bginfo.exe \\yourdomain\netlogon\template.bgi /TIMER:00 /nolicprompt


The commands above can be saved in a .bat file in Netlogon folder 

3.   3. Apply BgInfo logon script using a Group Policy:

To apply BgInfo logon script using a Group Policy, proceed like the following:

  • Create a new GPO then go to User Configuration > Policies > Windows Settings > Scripts (Logon/Logoff) and then double-click on Logon


  • Select the BgInfo logon script you created and then click on OK


After that, you need to link your Group Policy to the OU containing the accounts on which it will be applied.

-End
View Comments 0 Comments
Share Post   

vCenter 6.0 interface sucks

Thursday, September 10, 2015 - Posted by Keith A. Smith, in VMware, Journal of thoughts

As mentioned here http://bit.ly/1UrCpqN, I finally made the move back to vSphere and decided to go with version 6. There has been chatter over the past few years that, the release of a great new web client was coming. Well, it finally came and honestly, they would have been better off sticking with the fat client. Why..? You may ask. Because the interface is Flash! Yes, the same Flash that should have been deprecated by now, the same Flash that has more Zero-day vulnerabilities than a tennis net has holes. I don't understand why any company would develop an interface in Flash or Java at this point. I can here some people at VMware saying if we were to develop the vSphere 6 web client in HTML5 it would take more time. I think most if not all customers would say ok take the time, because HTML5 is the best way to go point blank!


I will say this, the vCenter doesn't totally suck


Positive:

1) New platform architecture 

2) Upgrade process is supposed to be a lot easier



Negatives:

1) Uses Flash — vulnerabilities, vulnerabilities, usability is terrible.

2) Uses Java — A catastrophe, Issues with every Java upgrade that are compatibility related,"security enhancements", vulnerabilities

3) Uses browsers & plugins — impacted by browser releases or changes, versions, vulnerabilities


I think that VMware needs to be more transparent about what they are doing with the replacement of this terrible Flash interface. I also think that they need to keep the TAM's informed so they can keep customers apprised of the progress.


-End
View Comments 1 Comments
Share Post   

Page  <1...1011121314...17>