Information about joeware mixed with wild and crazy opinions...
So tomorrow is supposed to be the end of the world… So I encourage you to hit the tip jar in the corner and donate your entire or most of your life savings or perhaps even $12.21, $1,221, or $12,212,012. If that last one, I will give you free support on all joeware tools for at least five years. It will make you feel great to give selflessly and make me feel great to see my bank account grow. At least for a day… Right?
Happy End of the World to all!
joe
In the Beginning…
The beginnings are rather simple, and maybe a little mundane; Larry Wall (Tim Toady) released version 1.0 to the newsgroup comp.sources.misc on the 18th December 1987 while working as a programmer at Unisys. Perl was intended, we believe, to be a Unix scripting language to make report processing easier borrowing from sh, Awk and Sed.
Perl 2 was released in 1988 and added more features and a better regular expression engine, this was followed by Perl 3 in 1989, Perl 4 in 1991 to coincide with the Camel Book, until finally we have Perl 5 in 1994. Perl 5 was a major shift in the release of version numbers which I will touch upon below. Perl 6 started its life cycle in 2000 with a different principle to other versions of Perl. It was a complete re-write of the language and would start as a language specification before a release leading to the now apocryphal ‘released in time for Christmas’ line.
Further reading see http://news.perlfoundation.org/2012/12/the-first-twenty-five-years.html
So I previously http://blog.joeware.net/2012/12/13/2650/ pointed out an article talking about AD Support in Samba 4.0. Upon further reading around on the Samba Wiki, white papers, and release notes etc, the article appears to be a little over generous on the functionality.
One thing specifically that I was shocked to read is this
In addition, the new version offers full interoperability with Microsoft Active Directory servers. A Samba 4 server can be joined to an existing Active Directory domain, and Microsoft Active Directory Domain Controllers can join a Samba 4 server.
which is directly contradicted by the Samba 4.0 Whitepaper at http://wiki.samba.org/index.php/Samba_4.0_Whitepaper
Active Directory Compatible Server
Samba 4.0 for the first time features an Active Directory Compatible Domain Controller.
The one setup as Active Directory Compatible Server supported out of the box with Samba 4.0 is this:
- There is only a single domain in the forest.
- There are no cross-forest-trusts (more explicitly, samba can be trusted but can not trust)
- Samba is the only domain controller in its domain.
These limitations are being worked on and will be removed in later 4.X releases.
The support for multiple domain controllers in a domain requires to flavours of replication:
- directory replication (for the user database)
- file system replication (for the sysvol and netlogon shares)
Of these two windows protocols, the directory replication is available in samba, but the file system replicatoin is still being worked on.
Note: homogeneous Samba 4.0 Multi-DC-Domains
Hence one can set up homogeneous Samba 4.0 Active Directory multi-DC domains, i.e. domains with multiple Samba 4.0 domain controllers and no windows domain controllers. For this kind of setup, one needs to set up an external substitute for the file system replication, for instance with some rsync-based shell scripts. One has to do this very carefully though, since the there is not concept of sysvol master role.
which appears to be contradicted by http://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC
You start samba as a DC in the same way that you start it as a normal server, just run the command ‘samba’ from the sbin directory of your installation.
When you first start Samba as a new DC in an existing Windows domain, you may find errors messages like these in the samba log file:
UpdateRefs failed with WERR_DS_DRA_BAD_NC/NT code 0xc00020f8 for 5344d0a6-78a1-4758be69-66d933f1123._msdcs.samba.example.com CN=RID Manager$,CN=System,DC=samba,DC=example,DC=comThis is caused by the Windows domain controller that haven’t yet run its Knowledge Consistency Checker (KCC), which means it has not yet created connections to the new Samba DC.
So perhaps things are not as shiny as indicated by The Register but hey, it is a start… Things should[1] only get better.
joe
[1] I am not guaranteeing this…
I had no idea they were still working on this… Could be interesting. Test well before putting these into production….
http://www.theregister.co.uk/2012/12/11/samba4_active_directory_support/
So I am starting to poke around and sort out how I want to rebuild my test lab setup as I have been ramping back up on using it and finding it is a little anemic occasionally. Currently I am running off of SuperFastVirtualMofo which is an Intel Quad box I built back in the spring (I think?) of 2007 with 8GB of RAM and upgraded over time to some 5-6TB or so of online storage capability. The primary use of the server is to host virtual machines for my testing of different environments.
My thought for the next generation is to build using a hot swap[1] iSCSI SAN box (+eSata just in case I am not thrilled with perf) instead of putting a bunch of disk into the server(s). Then I can have one or more smaller servers packed with RAM and a medium sized SSD for boot/system that plug into the SAN.
Initial thoughts have me thinking about the QNAP Product suite as I keep hearing good things about them, specifically I have been thinking something like the TS-469L/Pro or perhaps the TS-669L/Pro.
Oh I currently expect to be building the new server(s) with Windows Server 2012 Hyper-V. The old server I would likely use for backups.
Thoughts from the blog readers?
thanks, joe
[1] Having replaced two failed drives in the current server over the last 5 or so years without having any indicator lights or anything else as to which drive is bad was painful and I would rather avoid in the future. Plus doing it while the equipment is running is a bonus.
“The really really bad thing is that when it blows and goes viral in the media, no one is going to sit back and figure out that Company XYZ was being stupid, it is going to be that IT Provider ABC didn’t run the environment properly.”
-me
I have been asked a few times recently for MD-5 and/or SHA-1 digests for the various utilities. I put some perl code together last night to generate that information and I have added it to the versions.txt file that is on the website. I will likely slowly add it to the actual individual tool pages as well. I have also "compiled" the script with ActiveState’s wonderful PerlApp Utility from the Perl Dev Kit and uploaded that to the website as well so you can use it if you don’t currently have a tool for generating the digests.
It looks like:
F:\joewaretools>joewaredigest *.exe
joewaredigest V01.00.00pl joe@joeware.net November 2012
AccExp.exe 743215e8b481c4d83cb19d844f9c9574 eb5f827483002389dae0bb3b16f7387c1bf66b8d
AdFind.exe ff3dad91b266fee1ea107a2c9964349a 4acc9ddf7f23109216ca22801ac75c8fabb97019
AdMod.exe c64665b4d245dab287317e28b7f6ecd5 15ff3b3be83a1fd5582cb17a8edeaa9d1aebde3e
AdQueueLoop.exe 9db4f587fe9255025660686061e77a0a 5076ee44ad9c9cb074ba31333af0997b35b9ad43
ATSN.exe 430b0d6dc378b112d6669e1dd2c50440 a1b88b10541ef2a73bd0c08411c314898b9f5303
Auth.exe 3758b8df84e839c870be1923f790bb99 a6d1a2a560c74f39145a81be4918890af028b7ff
changepw.exe e7f36e96a2eb587dc13e170f4d2ecfed 078f89368ff6e1d1e20536b817ec4391131468b5
ClientTest.exe 37dcbd53a07a1058cdbac6c995f2c587 72f92b61c180b4f97033c8846a17ebd727589c8c
CPAU.exe 7100f979b8516b8c1ae6ff858435626e c6a596b10bc8fd05f8a13859fef8b2cf7a9360e7
DNSSrvRec.exe 2d36802ffe70e3328e62dd3094123af2 a25663bf9db368247aba79ef381830943932f1da
ELDLLExInstall.exe bd1c5fb5af14289fafaf4e994545dd81 207b7dc29090057396958feaec02c7d989b7ffd1
ELDLLInstall.exe 271d3fa6fc9a4e2981c268abee02af35 faf19566c4954d796f284d990bf99509bf05d1a2
ExchMbx.exe 2f373a9c206f5a2794cfc693f604d9fe 8d07815581f07b2262a6ba2a213ba7eceff81c4e
Expire.exe 3bfa82b554c5803dc809f343999642c1 7c0300da0049dc756e2ea91754c201d02510261a
FindExpAcc.exe d1b13d81b20e0fd6158b145f2fdd4213 b30b449f256edc82f4f489622f2507333966eb9d
FindNBT.exe 3b8d3657b36aec0fb7a0bebc4d88f0c2 a6139dc3a7f6d09e59a77c40977f2ea1f1e327de
FindPDC.exe 410279342c05c78673bcf67952993734 dec101ba2ed776db7e6b5827770af0c65a34da59
GCChk.exe 5d3049643055c3328a34faecba001339 826ee4a1a09811196f286395de502b4cb1612cc0
GetUserInfo.exe 541f3288a001970902b4fccf72ba2343 213f06ed5ac9e688816b4bbe73bf507994949964
joewaredigest.exe 9dce93eb13bdebd0deedec2c1c4e48f2 5480c03010b85dd56f7050f5765c412fb0c70d00
LG.exe d94bc7bc2417e60a734e9dba03bb01c9 534dd71b75b1af65c967b4b6f526b78859a52bfd
MachinePwd.exe c5080d587849d58960b893cdb59e0024 b606b266dad0b5db08182a446595dc7c50297ce2
MemberOf.exe c846cbbce2e994e7446ebda947a15e45 70028baf4655875e0968161a5061d658dc645cda
NetSess.exe f310584eb1538cb78ca8c225038b2e54 965013bf24513f9c312db9483f87d3c87e1b77ba
OldCmp.exe e1848235d8b33b654347a8126c9819ff 98e374fb09273209fa3517d39ef60e62b3a011e5
PSOMgr.exe 6a937c91f9cc3bee30973f4b458b622d 5a9d449f5a95909a7afd84dabf031e54a5058cf3
QLogoff.exe b8e7fe3cbb62434738c22646eeba60aa d524d0ee81d104d337049ea6c40e1f685a80e097
Quiet.exe 935809d393a2bf9f0e886a41ff5b98be 1ed3fc1669115b309624480e88c924b7b67e73bb
SecData.exe b8529e94362019eff4235e1b2d2f6514 542925dd6d05abb8d74413578ebd85908316ca9d
SecTok.exe 99f7e80c898c22a3fbe533290b041eef a63aa49372a3ca599421a77b34e65a7095d260bc
SeInteractiveLogonRight.exe d1ca0d6e932634546e9e1438ce13d345 910ddd53163c4c1c769fc52994a4a16d0290e7d3
ShrFlgs.exe 7586ff1e497938cad331f195f2ee6229 155aff9ebd025dc701006e7ecef6427dd8da73ef
SidToName.exe 0e696ea81217a1ff8776e9312056a703 bdfc8f240a9e44a4c8a52da6a8bdff3b1c427ae5
SNU.exe f366bc2e029979f331f1bedabd2d45ce 57b1d31667a6823581f1e777b52d8dc9915cf228
svcutil.exe 35a880716fd517f7d2b727857c48cda6 96a97e4ae44dd16a5b30e6506a0d37d0413cc8da
Unjoin.exe bd5137615c5f947be510c8b1d210d529 36cd5bf149e468a85a398b697bd8e8c7fa981c08
Unlock.exe a0537949f105fa16e367d535b272c9bc bc76333a5f6b10b162fa34b9ddf6a46fd65f1a88
UserDump.exe a14ac214dd83ecf75c5032ba1098c416 d263cd402c4d203c17aa0274c9082ddbac1240b3
UserName.exe dc31f02293a3914bfb813d6664165392 9a4483ae37170eec25b83d157c806438a1b51d2d
W2KLockDesktop.exe 6ac3acb478d4c39cafa25610708e12bd 72108f7602363064adc32c7e6f7b0d63bb958db8
WriteProt.exe 1410134ff602b0ea3719fbc52a02cfcd 253504025a3335bae43e14c9edea23b57b96b0cf
Command Completed.
Please see http://www.joeware.net/freetools/digest.htm for more information. 🙂
joe
A friend sent me this this morning, made me chuckle. 😉
If you didn’t have the ability or time to use the QR Code I posted yesterday, it was a QR Code to take you to the new dsWiki WIKI site I set up that was previously discussed here. Please check it out, it is a work in progress and I am looking for feedback. I want this to become a very useful resource for people out around the world working on AD and other LDAP servers.
The URL is http://dswiki.joeware.org or http://link.joeware.org/dswiki or http://link.joeware.org/adwiki
You will also notice that Google Ads will start popping up. I don’t really know what I am doing with it yet so it will be a learning experience to make it look good and be useful. And thoughts, ideas, or questions, let me know.
joe
[joeware – never stop exploring… :) is proudly powered by WordPress.]
