Skip to content

ivan

System Administrator Married With daughter That's all folks

Windows 10 Privacy

If you are using Windows 10, do yourself a favor and just use this tool http://www.winprivacy.de/english-home/

SharePoint 2013 Instalation Tips

Studying for SharePoint 2013 exam, I’ve decided to install it in my lab and as usual I had some issues. I was thinking to use SQL server on premises used for SCCM 2012 R2 test lab, but it is 32-bit, therefore, unusable. Due to the limited resources (You know, RAM goes first) I ended installing 64-bit SQL Server 2012 SP1 on the same server (standard 2012 R2) side-by-side with 32-bit SQL. It’s not the best practice, but it is OK for a constantly changing test lab. Installation was pretty straight forward, all prerequisites were already installed and in minutes 64-bit SQL server was in place. I have two pre-created domain accounts sqladmin and spsservice used… Read More »SharePoint 2013 Instalation Tips

Create an SCCM collection containing inactive clients excluding certain computers

Create a new collection and use the following query to select inactive agents, the part in bold is to exclude all computers with name stating with PCNAME% from it if needed, % is equal to * in sql so if your naming convention is pcname01, pcname02  and so on pcname06% will exclude pcname060, pcname061, pcname0600 and so on. If you want to remove one or two names only you can use (“pcname01″,”pcname02”) instead of pcname% select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_CH_ClientSummary on SMS_G_System_CH_ClientSummary.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_CH_ClientSummary.ClientActiveStatus = 0 and SMS_G_System_SYSTEM.Name not like “PCNAME%” One of the fixes for inactive clients could be found here First part… Read More »Create an SCCM collection containing inactive clients excluding certain computers

Don’t Ask……

“Don’t ask what the world needs. Ask what makes you come alive, and go do it. Because what the world needs is people who have come alive” – Howard Thurman

Windows 10 Nvidia Drivers Issue with Skylake

Yesterday I had a morning surprise by my PC, when I turned it on all I got was white pixelated flickering caused by GPU drivers update (automated in windows 10) Safe mode and all of the advanced repair stuff wasn’t working so out of options I just used “Reset my PC”. In order to avoid the issue in the future autoupdate feature was disabled through: Advanced System Settings –> Hardware Tab –> Device Installation Settings –> Select No Please note that this is all or nothing solution, there is no granular control what hardware to be updated, so after No you should update all drivers manually. Remark: Seems that Latest Nvidia Driver (at the writing… Read More »Windows 10 Nvidia Drivers Issue with Skylake

Tested guide for upgrade 2003 domain to 2012

Raise domain/forest functional level to 2003 Domain is raised from AD users and computers Forest is raised from AD Domains and Trusts Prepare AD for 2012 The command adprep is located on your Server 2012 disk under the \support\adprep Run in cmd adprep /forestprep If KB919151 is not installed adprep /forestprep will fail with “ADPREP.EXE is valid, but is for a machine type other than the current machine” – REMARK addprep.exe must be copied from x86(or x64) folder to the folder where all other files (sch1, sch2, and so on, schema.ini is also inside), then run it from there. Install 2012R2 server, join it to the domain and promote it as DC First add active… Read More »Tested guide for upgrade 2003 domain to 2012

SSL routines:SSL3_GET_CLIENT_HELLO:wrong version number or similar

After experiencing a pfsense log overflow with SSL routines:SSL3_GET_CLIENT_HELLO:wrong version number, SSL: 1 error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol and similar errors for a while I finally figured a way to reduce them to the more reasonable level by simply checking Disable webConfigurator redirect rule in the advanced settings. There are still some errors in the log though, however, way less than before. Remarks – Captive Portal is disabled, webConfigurator is accessible from Internet, pfsense version is 2.2.5-RELEASE (amd64) – there is a setting to completely disable lighthttpd logging (as it was before version 2) under settings of the system log