Jobs for cycling error logs
If it were me I would create a SQL Agent job for cycling the error log based on size or date. Run it a few times a day and you can even set up alerts to notify if the error log was cycled. 

CREATE TABLE ##Temptable 
(
[Archive #] tinyint,
[Date] datetime,
[Log File Size (Byte)] INT
)
insert into ##Temptable exec xp_enumerrorlogs
IF (
    SELECT [Log File Size (Byte)] from ##Temptable where [Archive #] = 0
    ) &gt; 5242880 --5MB
    BEGIN
    Exec sp_cycle_errorlog
    END
drop table ##Temptable


You could also change the IF statement or add an OR statement to look at the date and cycle if it is older than 2 weeks or however long you want. 

IF (
    SELECT [Date] from ##Temptable where [Archive #] = 1
   ) &lt; GETDATE() -14


EDIT: Archive for the date based cycle needs to be the previous error log. Log 0 will always return current date, since it is active, duh! 

As for moving them, you can keep up to 99 log files. Do you think your extended information needs will exceed 100 logs? If not, I would move the error log location to a disk that can hold 100 full logs and change the maximum number of logs.