Blog This! | Blogger Buzz:
'via Blog this'
Too bad it is just Blogger Specific.. But sure goes quick.
By this I mean, the Blog-This Extension that connects to blogger.com.. Link is above.
After this post I went and found a similar plug in that ties into some other content pages... All told these methods are easier than going to a web site, opening a new post, writing etc. If one can work in an extension the subject is at hand while one is actually writing... rather than this blank white sheet on this edit page I find myself in here.
Tuesday, November 29, 2011
You think you need one Server do you?
If you read the marketing spiel a Windows Server will do 1000 things. If you try to use a Windows server however you may easily find that you need, in fact 2, 3, 5 or 10 Servers to do all the work that is asked of it.
Take a look at the Terminal Server Farm here:
I dont even know if the Domain Controller is listed, much less the backup Domain Controller.
One Server for Licensing. One Server for Load Balancing, etc etc. Dont forget DNS. Don't forget Wins. Don't forget.. ad infinitum.
All this takes a lot of time to implement, not to speak of hardware and licensing expense. And then there is power. Virtualization helps, but the last I read, certain roles are not recomended for virtualization.. Domain Controlling is one. The Slowness of Virtualization would call into question having your Terminal Server be virtualized. Maybe the licensing server. Perhaps a backup Domain Controller, the DNS server etc (why are those not part of the primary Domain Control Role anyway). I suppose they generally are, but redundancy makes its call.
Terminal Services are, for sure, great tools. A functioning server can generally be accomplished more easily than the picture shows. Still, some very high costs are out there, especially if you are pushing the OS up from the client level.
Time to research VNC again.
Take a look at the Terminal Server Farm here:
I dont even know if the Domain Controller is listed, much less the backup Domain Controller.
One Server for Licensing. One Server for Load Balancing, etc etc. Dont forget DNS. Don't forget Wins. Don't forget.. ad infinitum.
All this takes a lot of time to implement, not to speak of hardware and licensing expense. And then there is power. Virtualization helps, but the last I read, certain roles are not recomended for virtualization.. Domain Controlling is one. The Slowness of Virtualization would call into question having your Terminal Server be virtualized. Maybe the licensing server. Perhaps a backup Domain Controller, the DNS server etc (why are those not part of the primary Domain Control Role anyway). I suppose they generally are, but redundancy makes its call.
Terminal Services are, for sure, great tools. A functioning server can generally be accomplished more easily than the picture shows. Still, some very high costs are out there, especially if you are pushing the OS up from the client level.
Time to research VNC again.
Google Pulling the Plug on Notebook..
One of the best pieces of software from Google, and for that matter anyone, has been Google Notebook. Unfortunately, back in 2008, after I had been using it for about a year, Google stopped allowing new signups. They told all of us users that our Data is not going anywhere... we just couldn't do the cool sharing we had been doing... at least not with new invites.
Well here we are 3 years later and the data is going away. Well, actually they are exporting it all to Google Docs. I just did a "test export" before their auto export... At least something.
I will miss Google Notebook. I have been using Evernote in its stead. No where near as good for my usage, except for the fact that it actually works on my Phone plus my Computer... G Notebook certainly could have pulled this off.
What is the difference? I think it is the Hierarchy that could be made in Google Notebook. The Notebook, Sections and Notes part, with the ability to very very easily move things around, search and more.
And what of Trust? Well we thought Google Notebook would be for the long term. We assume, from the name, that Evernote will be forever. None of it. Palm notes are dead. I expect X-Marks maybe short for the world. Organize and make redundant. About all we can do it seems. Try Tracks Appliance and do it yourself: Keep on top of it. Try to recreate Google Docs. This might be the best solution.
Well here we are 3 years later and the data is going away. Well, actually they are exporting it all to Google Docs. I just did a "test export" before their auto export... At least something.
I will miss Google Notebook. I have been using Evernote in its stead. No where near as good for my usage, except for the fact that it actually works on my Phone plus my Computer... G Notebook certainly could have pulled this off.
What is the difference? I think it is the Hierarchy that could be made in Google Notebook. The Notebook, Sections and Notes part, with the ability to very very easily move things around, search and more.
And what of Trust? Well we thought Google Notebook would be for the long term. We assume, from the name, that Evernote will be forever. None of it. Palm notes are dead. I expect X-Marks maybe short for the world. Organize and make redundant. About all we can do it seems. Try Tracks Appliance and do it yourself: Keep on top of it. Try to recreate Google Docs. This might be the best solution.
Thursday, October 13, 2011
Computing landscapes are changing faster than we know.
What were normal protocols a year ago even are almost forgotten. Older Data Methods are becoming more and more difficult to maintain, while new systems pervade, their ease and flexibility is still for the future.
Cases in Point: FileMaker Pro and FoxPro. Two of the leaders going back to the 80's are either esoteric or moth balled. They do still, in general work (not that I have tried in Windows 7 to be honest). MySQL and variations like Postgre, MSSQL etc are the new standards... Theoretically systems like Crystal still tie these all together and let you at least organize the data. But being fast and fluent on the earlier systems does not bring much in terms of skills towards the new systems.
In other regards the new modus of Web Centric computing, balanced with a level of "smartphone" checkups is becoming the standard. Having an active Windows Client/ or Mac Client / or Linux Client are still the base stations from which to work, but that which is being worked upon is less and less actually on the desktop.
All for the good. Perhaps not a Whazup at all... But it is likely that the skills and knowledge of the old systems are often being lost. Perhaps it will not be important except for forensics.. still "how we got here" will be important to understand. How we go forward, in control of our data, likewise will also be important, and not always obvious.
Onward ho.
Cases in Point: FileMaker Pro and FoxPro. Two of the leaders going back to the 80's are either esoteric or moth balled. They do still, in general work (not that I have tried in Windows 7 to be honest). MySQL and variations like Postgre, MSSQL etc are the new standards... Theoretically systems like Crystal still tie these all together and let you at least organize the data. But being fast and fluent on the earlier systems does not bring much in terms of skills towards the new systems.
In other regards the new modus of Web Centric computing, balanced with a level of "smartphone" checkups is becoming the standard. Having an active Windows Client/ or Mac Client / or Linux Client are still the base stations from which to work, but that which is being worked upon is less and less actually on the desktop.
All for the good. Perhaps not a Whazup at all... But it is likely that the skills and knowledge of the old systems are often being lost. Perhaps it will not be important except for forensics.. still "how we got here" will be important to understand. How we go forward, in control of our data, likewise will also be important, and not always obvious.
Onward ho.
Wednesday, April 27, 2011
NT Domains, then Wink2K Win2k3, Win2k8 Domains, then Samba NT Domains bring us full circle
Microsoft hit a home run with their NT Domain methodology... Then the Internet started to "take ownership" of the "Domain Model" so Microsoft updated Windows 2000 with DNS level controls in their new Active Directory Domains..
All fine and dandy unless you really want a secure system and you didn't even want to Mix the Internet with your "office space"... It works, but it seems to need 3 servers to trust it and make sure it works.
Windows 2003, then Windows 2008 Servers all had their improvements and complications, but in my experience they also add complications to the management of a small system (and also cost). For me the domain needs to be about defining the network and getting some work done. It is not about getting a 3 level certification in IT protocols blessed in orthodoxy.
Recently I have started testing a Samba (Ubuntu based) Domain Controller that emulates the NT Domain on a Linux Stack. So far, pretty good.. Fast performance and reliable. In the end it is something else to learn If I really want to stick to it. That said, I pushed go, got it turned on, have attached 3 computers to the Domain and its been running for a week without any problems.
The important part is that it is being developed and continued by an active group (unlike MS NT , Win2K at MS.. in factwhy don't they open source NT?).. I have a Win2008 Server running in the Samba Domain just for comparison. The beauty of this is that about anything including Win2007 and my Windows 7 Machines can join the Samba Domain. My Windows NT Domains are not so friendly w/ Windows 7. Still, I get the simplicity of a simple domain structure that I grew to appreciate on the old NT Model.
There are many things to learn in life. One I am hoping to learn is not to spend too much time on Microsoft systems that will be thrown away before I am actually done using them. Putting Terminal CAL's on that 2008 Server is not something I am running to spring for either, though this may be one of the only arguments for not jumping ship entirely.
Try the Samba Domain controller: A good one is http://www.turnkeylinux.org/domain-controller:
All fine and dandy unless you really want a secure system and you didn't even want to Mix the Internet with your "office space"... It works, but it seems to need 3 servers to trust it and make sure it works.
Windows 2003, then Windows 2008 Servers all had their improvements and complications, but in my experience they also add complications to the management of a small system (and also cost). For me the domain needs to be about defining the network and getting some work done. It is not about getting a 3 level certification in IT protocols blessed in orthodoxy.
Recently I have started testing a Samba (Ubuntu based) Domain Controller that emulates the NT Domain on a Linux Stack. So far, pretty good.. Fast performance and reliable. In the end it is something else to learn If I really want to stick to it. That said, I pushed go, got it turned on, have attached 3 computers to the Domain and its been running for a week without any problems.
The important part is that it is being developed and continued by an active group (unlike MS NT , Win2K at MS.. in factwhy don't they open source NT?).. I have a Win2008 Server running in the Samba Domain just for comparison. The beauty of this is that about anything including Win2007 and my Windows 7 Machines can join the Samba Domain. My Windows NT Domains are not so friendly w/ Windows 7. Still, I get the simplicity of a simple domain structure that I grew to appreciate on the old NT Model.
There are many things to learn in life. One I am hoping to learn is not to spend too much time on Microsoft systems that will be thrown away before I am actually done using them. Putting Terminal CAL's on that 2008 Server is not something I am running to spring for either, though this may be one of the only arguments for not jumping ship entirely.
Try the Samba Domain controller: A good one is http://www.turnkeylinux.org/domain-controller:
Subscribe to:
Posts (Atom)