Home networks are becoming more complex and Internet service providers leave configuration to the user. This can unknowingly lead to vulnerable and slow networks. We will optimize your network without sacrificing security.
Now that cloud computing is affordable and reliable many small businesses decide against on-premise servers. But managed cloud servers still require experience to setup and edit. We have experience and are prepared to work in the cloud or on-premise.
Most large businesses need constant attention. However there are some that don’t rely heavily on technology or are tech-savvy themselves. If you ever have questions or want advice we are here to help anytime.
Resetting a forgotten password Windows 10 (Home, Pro, Enterprise) or Windows Server 2012 (R2, Essentials) without installation media, in a virtualized environment, or a RAID configuration.
Recently we needed to reset the password for a Windows Server 2012 R2 Essentials machine. A quick Google search brings up this article (click for link):
These steps work for a vanilla OS installation and if you still have your original installation media, however any customization such as RAID or virtualization renders them useless as the command prompt can not find the System32 folder resulting in the error: “The system cannot find the path specified.”
I have had my Fabtotum for a little less than a week now and spent most of my free time with it. As someone who is 100% new to 3D printing I wrote some of my challenges and observations below.
Unboxing the printer was straight forward and with the help of the video on the website I was able to login to the dashboard. It kept bugging me about not being connected to the Internet even though it was.
The first setup took awhile. The bed leveling process never seemed to give me the same result twice and added a probing for each corner every time I ran the test that made it take longer. I received the green OK boxes for all four corners and moved on. Later I learn this test is good to get the bed somewhat level but is not that precise. I removed the cover to add the spool and found the magnets had come unglued from the outer panel. Hoping these aren’t signs of more things to come.
My first print was an attempt to print the Fabtotum keychain and the filament didn’t stick to the bed. After some trial and error I realized the head wasn’t close enough and raised the bed and was able to print a good looking keychain with sharp edges and smooth lines. I moved on to Marvin and got about 50% of the way through when the probe knocked the piece over. I aborted the print with the emergency button and the machine freaked out hitting the end stops and probing areas off the bed. Whoa, shut the machine down and make a note of not to use that button again.
After that scare I decide to calibrate again and try to reprint Marvin. I still wasn’t satisfied with the calibration procedure. I slowed the print speed down to 70% and printed an alright looking Marvin.
At this point I was excited and ready to print some of my own files that I had downloaded. I tried to upload the file and was told it doesn’t accept .STL. After 30 minutes of trying to convert (splice) the STL file to .GCODE in MacOS I gave up and jumped over to windows. Success! MacOS did not allow me to enter custom endpoints so the file would not print.
My girlfriend wanted the Cute Hug Me Ghost from Thingiverse as a desk ornament so I figured that was a good place to start. I slowed the print to 70% and started out but was left with this mess:
I realized if I was going to slow the print head down I would also need to slow the flow of the filament or else I would continue to have these issues. Damn these slider bars to adjust speed, flow, and temp SUCK. I would love to be able to type in a value. A few failed ghosts:
I gave up with the ghost and decided to move on to something with less layers. Last year in anticipation of my printer I purchased an FPV drone from a company Tilt that sends you all the electronics and expects you to 3D print the frame. A small part printed easily but still had some issues in the layers:
After some more reading online I decided to try and clean and lubricate the filament before it entered the bowden tube. I found this part online and printed it:
I swapped spools, installed the new lubing tool, calibrated, and printed my best looking part yet:
Tried the ghost again:
At this point I had gained some confidence and wanted to try and print something bigger. My first attempt at the base plate for my drone left me super confused. The filament was too thin on the right side of the bed, and not adhering to the left side. I began to think the bed might not be level (this is what I was hinting at earlier). I decided to give the bed leveling procedure one last shot and spent some hours working to achieve this:
I tried to print the part again the the problem was worse than before. I realized my other parts were so narrow on the X/Y axis that I never noticed the issue until I printed a larger part. I cancelled the print and retried with the auto bed leveling option. Nothing happened? Tried a few times with the same result. I moved on from that and after some research found other people had similar experiences as me and had made a tool made for leveling the Fabtotum bed:
I didn’t have much luck with the tool because the bed wasn’t level enough to print out a part to use for calibration. Frustrated and clicking around the options I found I had the wrong head selected. I put the new head in and felt the instructions for probe height were better in this process than in the first set up. I found that when calibrating if the head is not drawing ink on the paper it is definitely not close enough. It seemed to work best if the probe even puts a slight indentation in the paper:
With the proper head selected I calibrated everything again. Then I noticed there was a software update. I was full of hope now: the correct head was selected, the probe was close enough, the bed was level(ish?), and the software was up to date. I test printed a keychain and had one of my worst prints yet. Complete disappointment. Exhausted from working all week and staying up all night I give up for the day.
The next morning I had the day off and woke up refreshed. I calibrated everything and even adjusted the probe angle calibration in hopes that this might help. I started to print the base plate again and it was terrible. However I was beginning to notice I could see most imperfections during the first layer of the print. Since this print was so large the first thing the probe did was create a perimeter for the piece that outlined almost the entire bed. Looking at the perimeter of filament on the bed was enough for me to see where the bed was too high/low. I cancelled the print (not aborted!) as soon as it finished the perimeter and tried my best to level the bed using this method. The next print was a little better so I let it go a little further, then cancelled and tried to level it a bit more. After 8-9 of these cancelled prints the bed was finally level enough for the entire first layer to apply successfully. I monitored it for the entire first layer then went to bed. I woke up to this:
I still have a lot more to learn but am happy with the my first week with the printer. Once I get a grasp of printing I will move on to scanning/milling.
There has been a lot of talk about the security and ethics of Cloud computing for law firms. After thoroughly researching we decided to try Microsoft’s Office 365. This is about our migration and what we have learned by using Sharepoint the past few months.We began with moving our emails from an on premise Exchange server to an Office 365 hosted Exchange server. After getting comfortable with Microsoft’s hosted services we decided to experiment with SharePoint, recently renamed to One Drive for Business. Our on premise file server ran a variation of Linux. This made starting the migration difficult because we had been building our directory without the constraints of Windows OS (MAX_PATH and character limitations) for the past few years.
Microsoft makes a tool called One Drive Filechecker that will scan your directory and give you a list of file paths that will not work in SharePoint. However when you’re dealing with hundreds of thousands of files this can quickly become overwhelming as the error list starts growing. We utilized a tool called Shareprep which allows you to replace characters in file names in bulk as well as truncate file paths.
At this point the directory was cleaned and ready to be moved to SharePoint. Microsoft makes a great desktop application called One Drive for Business that is supposed to make this easy. Unfortunately it has a maximum file limit of 20,000 files if it is synced with a library. This creates an issue if your firm has over 20,000 files like most do.
To get around this we mapped our SharePoint URL as a network drive. We then used the command prompt to move files from the local drive to SharePoint. It was still a long process and we decided to do it over a weekend to prevent confusion for the attorneys. We broke our local drive up in sections and uploaded it in 10GB batches.
Overall we are happy using SharePoint to host our files. The drive mapping is almost seamless and the attorneys enjoy being able to access files out of the office without using the VPN. They also have the option of accessing it from any web browser if they don’t have their laptop, and Office 365 provides browser based Microsoft Office programs. When browsing the SharePoint mapped drive there is little difference in speed from a local drive.
We don’t like the check in/check out feature. This causes problems when a user forgets to check a file back in because another user can’t edit it or delete it without overriding their check out. This seems to happen more often with PDFs. We lost the ability to scan directly to our SharePoint URL and were forced to find a workaround for that.