Windows

Windows XP, 7, 8 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

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

This Pc opening very slow Windows 8.1

Yesterday This Pc started to open very slow on my Windows 8.1 making me angry of course 🙂 Today I had time to dig in and at my suspicion that a network share or something  similar is causing the issue was close enough. I disabled Windows Media Player Network Sharing Service and Voila – Everything opens so nice and smooth again. So far i am satisfied and with the result, My pc is feeling (visibly) faster and this service is not missing me at all. By default it starts automatically, so it’s up to you to disable it or let it start with the next restart.

Install/Uninstall Feature PowerShell Server 2012 Quick Notes

To get the list of all features(feature names are in the second column, Windows PowerShell cmdlets are not case-sensitive): get-WindowsFeature To uninstall completely a feature: Uninstall-WindowsFeature featurename -remove If -remove is not used the feature will be listed as available, however, it won’t be removed from the harddrive. To install a feature after it’s removed we need an installation wim file as a source. To Mount a Windows WIM to the file system: Get Info what’s in the wim file, features cannot be mixed, that’s why indexes are important – if core is installed  then find which index belongs to core, because wim file contains more than one windows editions dism /get-wiminfo /wimfile:wimfilepath (Example if installation… Read More »Install/Uninstall Feature PowerShell Server 2012 Quick Notes

Log Off User remotely – cmd

If you ever wondered how to log off user remotely (or locally) via command line try this. As usual membership of the local admins group is needed. Start cmd with elevated privileges. check logged user and their session number with qwinsta: QWINSTA /server:computername Memorize the session ID and use the logoff command: LOGOFF sessionID /server:computername.