When I created the HWCDI blog app, I followed Miguel’s tutorial. I started hosting it in ‘production’ and didn’t follow his exact setup instructions. I’m not running in a venv (bad?) I also left out a vital note Miguel clearly covered. I was making my edit blog post page a little more robust, adding the[…]
-> System Settings -> Shortcuts and Gestures -> (On Left Bottom) Global -> (Top Drop Down (Component)) KWin -> (Action Column) Switch One Desktop ->(Click it) -> Custom -> Input -> (Shortcut) (I do Ctrt+Alt+ArrowCorrespondingToDirection)
Once you decide to go SSL, you realize browsers have come a long way. The little security icon in Chrome indicated I had some issues with my site. That not everything was using https… Hmmm… I came accross the flask-SSLify module: https://github.com/kennethreitz/flask-sslify That didn’t solve the warning indicator. The thing NEEDS to be green! Digging[…]
(Super+R -> cmd -> Enter) C:\Users\colin\bin>wmic wmic:root\cli> (Super+UpArrow) (Ctrl+C) If you’re reading this, use the command line sometimes on M$, and you haven’t already, install http://git-scm.com/download/win Choose option 3 for the PATH question. You won’t regret it.
Sooooo… I got a little jumpy and bought ZFSFTW.com .org .net .info and a UCC cert. (I also had to renew colinworld.com so of course I did and .org .net .info as well.) Now I need to make use of the SSL cert. Use. My domains NEED a signed cert. … whatever, I bought it.[…]
I needed to grant one of my techs local admin access to one of our DCs. (Don’t ask, it needed to happen temporarily) Anyways, here’s how: net localgroup Administrators $DOMAIN\$USERNAME /ADD
Enabling all AD User accounts in an OU is also a quick one liner: Get-ADUser -Filter * -SearchBase “OU=HWCDI,DC=HWCDI,DC=local” | Enable-ADAccount
Resetting the password for all users within an OU is a quick one liner (in CMD): dsquery user OU=HWCDI,DC=HWCDI,DC=local | dsmod user -pwd NewPassword1!
Earlier, I realized My AD export is not grabbing all object attributes. In the original AD export script, I was actually defining fields to export using -l argument: -l “cn,givenName,objectclass,samAccountName” You can get pretty complex with LDIFDE.exe (for help see): #> ldifde /? Omitting the -l argument in the export script exported ALL object attributes.[…]
Now we need to import our user objects into a new domain. Spin up a new Windows Server 2012 R2 VM, add necessary roles for AD. Create a new OU in AD for your imported users: dsadd ou “OU=HWCDI,DC=HWCDI,DC=local” Parse / modify your usersFile.ldf file however you’d like, just ensure each object’s entry is updated[…]
