Archives

Camtasia - .camrec file to .avi conversion

Posted by technick.85

Turns out that .camrec files created by Camtasia are actually zip files that contain the .avi that was recorded. You can use a program like 7-Zip to extract the .avi file

And if you want to save some space, you can always compress that .avi file with WinRar. It looks like the .camrec zip file is not compressed - however I've been able to take a 5GB+ avi file from Camtasia and compress it down to under 400MB.

Share |


    • Exchange 2007 - Unified Messaging Server Role SBS2008

    Posted by technick.85

    From my archive notes: 10/25/2012

     While trying to integrate an Avaya IP Office into Exchange 2007 I found that there was no "Unified Messaging Server Role" service installed. So I went to the control panel to change the install for Exchange Server 2007 to enable that Role. Two address paths were defined when adding this service.

     First for the Exchange Server installation files:
    C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\EXCHSRV80

     Second for the Exchange Server installation path:
    C:\Program Files\Microsoft\Exchange Server

     Our server did not have any folder located in the default installation files path and I didn't have my Exchange server install CD handy. Looking at several guides online, users have complained that using the original files from their install CD caused issues. So I went online and found the latest service pack that I had installed and decided to extract the files from there. Turns out I had Exchange Server 2007 Service Pack 1 (x64) installed.

     I was able to download the "Exchange Server 2007 Service Pack 2" files from here:
    http://www.microsoft.com/en-us/download/details.aspx?id=4479

     The exe file was about 884 MB. After extracting the file using WinRAR, the file size was about 1.22 GB (now I can see why the files were not on my server). At one point or another, a previous tech had cleared out these files to save space on the server. From my workstation where I extracted the files, I opened the shortcut to my server and copied the files to the C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\ under a new folder named "EXCHSRV80"

     I decided on waiting a couple of days for the weekend as I didn't want to take the server down for updates in the middle of the workweek...

     Notes and Resources:
    http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/64a9409a-e57a-4431-932e-b1426a17f66e

    Deep research on this issue:There are two options (if you need to use the SBS DVD 2). Pick one.
    ·  Copy the CMPNENTS\Exchange12 directory from DVD2  to C:\Exchange 12
    ·   Add a registry key :
    MediaPackage  REG_SZ \CMPNENTS\Exchange12\
    under:  HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\461C2B4266EDEF444B864AD6D9E5B613\SourceList\Media
    More information for your reference:
    PRB: Error 1706 "No Valid Source Could Be Found" When Installing MSI File from Removable Media
    http://support.microsoft.com/default.aspx/kb/299803

    Share |


    • Avaya CallStatus EAccessviolation error

    Posted by technick.85


    Found this guide to stop the EAccessviolation error associated with Windows 2003 server when running Avaya's CallStatus program. A user named cascadia on the http://www.pbxtech.info Forum had this to say and it worked for me:

    ====================

    There is a very easy fix to this. I was advised to update the server fully with MS patches. Did that, but no help. So I did the following on a hunch and it worked!

    My Computer > Properties
    Advanced Tab
    Performance > Settings
    Data Execution Prevention Tab
    This is turned on by default with a blank exception list.
    Click Add...
    Locate your copy of callstatus.exe
    Mine was in C:\Program Files\Avaya\IP Office\CallStatus\callstatus.exe
    Click Apply > OK > OK

    And now you should be able to execute the Call Status monitor and run it like you used to.

    Source: http://www.pbxtech.info/showthread.php/3114-EAccessviolation-error

    Share |


    • Old Notes - Upgrade from EXC2007 SP1-SP3

    Posted by technick.85

    Souce & Resources:
    http://msmvps.com/blogs/bradley/archive/2011/03/11/exchange-server-2007-sp3-does-not-update-the-exchange-server-active-directory-schema.aspx

    EXCHANGE SERVER 2007 SP3 DOES NOT UPDATE THE EXCHANGE SERVER ACTIVE DIRECTORY SCHEMA:

    Exchange Server 2007 SP3 does not update the Exchange Server Active Directory schema: http://support.microsoft.com/kb/2457729/en-us?sd=rss&spid=10926
    After you install Microsoft Exchange Server 2007 Service Pack 3 (SP3) on a computer that has Exchange Server 2007 Service Pack 2 (SP2) installed, the Exchange Server Active Directory schema is not updated.

    This issue occurs because the Active Directory schema version information in Exchange Server 2007 SP3 is the same as in Exchange Server 2007 SP2.
    Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
    Let's translate....
    If you installed Exchange 2007 sp2 on pretty much any box with Exchange including SBS 2008 you will find that after you apply SP3 you can't add any new receive connectors.
    To work around this issue, run the Setup.com /prepareschema command.
    Let's translate again:  To now fix this issue since the install was supposed to upgrade the schema automatically, download SP3 again (or if you still have it on the box find it again) and follow the info in this blog post -- http://blog.korteksolutions.com/cant-create-a-new-receive-connector-after-installing-rollup-1-or-2-for-exchange-2007-sp3

    To avoid this issue, run the Setup.com /prepareschema command before you install Exchange Server 2007 SP3.
    Let's translate one more time.  If you jump from Exchange 2007 sp1 to sp3 you'll avoid this issue altogether.  It's only those of us who kept our servers reasonably up to date that got nailed on this.  This only impacts those who installed SP2 and then SP3.  If you've already installed SP3 and you were on SP2 you can't avoid the issue since you didn't know it existed in the first place.  Nor may you realize that you can't build a new receive connector until you go try to build one. 
    So if you are still on sp2 and haven't gone to sp3 (like me) as you were waiting to see if there would be an automatic fix to this issue, there won't be.  Just be sure to run that prepare schema command before you apply sp3 and all will be well.  If you already did apply sp3 and can't do a receive connector, don't worry, merely manually running the command to upgrade the schema will do the trick.
    Filed under: 

    # re: Exchange Server 2007 SP3 does not update the Exchange Server Active Directory schema:

    Monday, March 28, 2011 12:23 PM by Andy Helsby
    In my case I wasn't able to install a new connector until I removed the rollup and then created them. Updating the schema did not make any difference. It was thanks to Kyle's blog that I got my server working though.
    As Kyle doesn't allow comments to this older post, my comment was on the next available post - blog.korteksolutions.com/after-converting-a-sbs-2008-server-from-physical-to-virtual-with-backup-exec-system-recovery-sysprep-hangs

    http://blog.korteksolutions.com/cant-create-a-new-receive-connector-after-installing-rollup-1-or-2-for-exchange-2007-sp3/


    Can’t create a new Receive connector after installing Rollup #1 or #2 for Exchange 2007 SP3

    After you install Exchange 2007 service pack 3, and or rollup #1 or rollup #2 and you attempt to create a new receive connector, you receive the following error:
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:00:00
    test
    Failed
    Error:
    Active Directory operation failed on SBS01.ks.local. This error is not retriable. Additional information: The parameter is incorrect.
    Active directory response: 00000057: LdapErr: DSID-0C090C26, comment: Error in attribute conversion operation, data 0, v1772
    The requested attribute does not exist.
    Exchange Management Shell command attempted:
    new-ReceiveConnector -Name ‘test’ -Usage ‘Custom’ -Bindings ’0.0.0.0:25′ -Fqdn ‘test.test.com’ -RemoteIPRanges ’0.0.0.0-255.255.255.255′ -Server ‘SBS01′
    Elapsed Time: 00:00:00
    image


    This is caused by service pack #3 not extending the schema properly, or not at all. To resolve this issue, download service pack 3 again at http://www.microsoft.com/downloads/en/details.aspx?FamilyID=1687160b-634a-43cb-a65a-f355cff0afa6&displaylang=en and then extract it.
    Open a command prompt and go to the extracted folder. Now execute the following command:
    Setup.com /PrepareSchema

    image
    Now attempt to create your receive connector, and it will work fine. Please note, you do NOT have to remove rollup #1 or rollup #2 to fix this issue. I found one post that mentioned waiting for rollup #2 to come out to fix the issue http://msmvps.com/blogs/bradley/archive/2010/10/12/can-t-do-a-new-receive-connector-after-exchange-2007-sp3-rollup-1.aspx , but the issue is not fixed in the rollup as it is a schema extension that was introduced in service pack #3. Upon further reading and investigation, on the Microsoft TechNet site, at http://technet.microsoft.com/en-us/library/ff607233(EXCHG.80).aspxit clearly states
    “You must prepare Active Directory and each domain before you perform the first installation of Exchange 2007 SP3 in an organization. This process includes updating the Active Directory schema for Exchange 2007 SP3″
    image
    Guess no one read this part, including me!

    Share |


    • Add User to "Log on as a service" on SBS2008 DC

    Posted by technick.85


    Open Group Policy Management from the Administrative Tools.

    Right click the ‘Default Domain Controllers Policy’ and choose ‘Edit’.

    Choose Computer Configuration –> Policies -> Windows Settings –> Security Settings –> Local Policies –> User Rights Assignment and double right click in the right pane ‘Allow log on locally’.

    Click ‘Add User or Group’.

    Click Browse

    Type in the box ‘besadmin’ and click ‘Check Names’.

    Click ‘OK’.

    Share |


    • When Upgrading your Video Card...

    Posted by technick.85

    Always remember, when upgrading your video card to make sure your power supply can handle it! That is all.

    Share |


    • Working with Large Lists

    Posted by technick.85

    Photo by Stuart Miles
    Bossman got you facepalming on your latest project? Working with large subscriber or customer information lists can be a headache. You may run into a project where you have to combine several types of lists with different column information and they don't match up with your new system. You might have to prune, merge, cut or otherwise make sure a huge list is clean/tidy. Microsoft Excel can handle csv files, but keep in mind that Excel does have its limitations:

    Microsoft Excel has size limitations:

    Here are some alternate tools and information I've run into to help maintain your larger lists:

    CSVed
    For managing large CSV files (think super-excel):
    http://csved.sjfrancke.nl/

    CSV Splitter
    For splitting huge CSV files (can keep header and apply to split files):

    Combine using Command Prompt
    How to combine several CSV files into one file using cmd:

    Share |

  • Filed under: , , , , ,

    • Move IIS Log Files in SBS2008

    Posted by technick.85

    C:\ Drive on your server looking a little... Fat?
    Here's a good tip to save you some C:\ drive space in SBS2008. You can move the location of your IIS log files, potentially freeing up some significant space on your system drive. The default location of those files is C:\inetpub\logs\LogFiles. In this example, I'll explain how I moved them to my "E" drive under E:\inetpub\logs\LogFiles instead.

    First thing is to create a new folder where your IIS log files will be saved. I decided to use the same naming scheme as the default but just on a different drive. In this case, I went to my "E" drive and created a folder named "inetpub" with a subfolder named "logs" inside. Inside of "logs" I added a new subfolder named "LogFiles". The full path looks like this - E:\inetpub\logs\LogFiles

    As with most things, you'll want to create a backup of your log files to be safe.

    If you're running Windows Small Business Edition 2008, go to the Administrative Tools menu (located in the Control Panel or on your Start Menu) to open the "Internet Information Services (IIS) Manager". You want to select your top level item - it should look something like "SERVERNAME (DOMAIN\username)". On the right menu, you'll see an icon for "Logging" that you'll want to open.
    See that Logging icon, double-click it

    Once in your "Logging" menu, you'll want to change the Directory location to your new folder. You can either type/paste the new location or browse to the folder you want to use. When done, select the "Apply" action on the far right pane. 

    Make sure to hit "Apply" when you're done!


    Each of these areas have menus like the first where you can change the "Logging" directory from the default to one of your choosing. Rinse and repeat the above steps with each of these sections to make sure they're all redirected:
    Each of these have Logging settings, check all that you have

    You'll notice when this is done that your old Log files are still in your C:\inetpub\logs\LogFiles folder. I just cut and pasted those subfolders into the new directory. If it asked me to replace any of the files I told it to move but keep both files (rename).

    I freed up a couple of gigabytes and still was able to keep my logging active. You never know when you'll have to reference them so it's always good to keep them around.

    Share |

  • Filed under: , , , ,

    • Program Open But Can't See - Invisible!

    Posted by technick.85

    This screenshot is actually for an invisible folder, but you get the point.

    Yesterday I had a pile of stuff fall on my keyboard while a program was open. Today, the program opens but I can't see it.

    The program was open but invisible on the screen in Windows 7. The window shrunk to a size of zero and wouldn't even let me maximize to view! Re-installing didn't work. Right-clicking the preview window and selecting Maximize wasn't a option. Alt+Tab and WinKey+Tab didn't do the trick either (although WinKey+Tab looks pretty cool). Cascading or stacking the windows by right clicking the start menu bar didn't do jack!

    I had to use WinKey+Up Arrow to maximize the window (after I clicked on the preview window on the start menu bar) and then drag the title bar down to un-maximize. At first I just clicked un-maxmize, but it dissapeared again. When it was back to normal, I closed and re-opened to make sure the size stuck. Sure enough, it did! See below for some more useful shortcuts:

    Use WinKey+Shift+M to restore minimized windows to the desktop.
    Use WinKey+Up Arrow to maximize the current window.
    Use WinKey+Left Arrow to maximize the window to the left side of the screen.
    Use WinKey+Right Arrow to maximize the window to the right side of the screen.

    Share |


    • Newer Posts Older Posts