Jump to content

TwoJ

Member
  • Posts

    51
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About TwoJ

Recent Profile Visitors

1,100 profile views

TwoJ's Achievements

0

Reputation

  1. 1) - i think this will depend on if you are talking 32 or 64 bit versions, i have a similar job of going from 2003 x86 to a 2008R2 x64 and most info you find on the internet (even on technet) doesn't mention that a x86 printer driver isn't going to work on x64. Sounds obvious but that one of the hardest part of doing the conversion. I think the best method is to add the x64 drivers to the 2003 print server, then on the 2008 install the print management role, you should be then able to add another print server to the print management console (i'm not positive in 2008 but its possible in 2008R2), after that you can right-click the 2003 print server in the 2008 Console and select export - which will save all the settings to a file, then you right click your 2008 print server in the console and import. I don't think it will import permisssions but you might need to report on that - i am curious on it. Personally i would assign printers by Security groups so that its very simple to reapply permissions if necessary. 2) - use the robocopy tool (built in with 2008), you can read up on all the switches, but i think you want is something like /copyall or /DATSOU, these might be wrong so read up on the right switches. There also exists a few GUI front-ends for robocopy which is why i don't remember the switch. BTW - both servers need to be in AD for this to work. I suggest testing before a real migration.
  2. I was hoping to do most of it in a powershell script since it would allow more of a universal application, but i'm open to all types
  3. I'm doing some testing with Server 2008R2 and i've been looking around for some scripts to do some post install configuration. I know there are some powershell scripts to do some configuration of all types of stuff but has anyone made a sort of batch, command or powershell script something like the regtweaks for XP that deals with all sorts of configurations and settings for windows, stuff like change the view of the control panel, set the time zone, enabling the Remote desktop, changing the folder views, etc. Ideally it would be better in powershell since it can be used remotely, but i'll take what i can get! thanks PS - I'm not trying to do this in an unattended install manner, it would be post-install
  4. Hi Mike If i understand correctly you are trying to export from Windows mail on one computer and have those emails imported into outlook on a 2nd computer? As i said, i haven't used windows mail so i don't know the format it uses. If you are trying to find where WM (Windows Mail) is storing your emails do a search through the computer for the extention (*.dbx for Outlook Express) and/or look in the default locations. If you've copied the files you need to dump them into the folder for WM mentioned in my other post - then make sure WM has the emails in it. After that close WM and open outlook and then do the import from 'internet mail and addresses' you probably can look for some info from MS to show how to do it as well
  5. I would flush your email account and set it up again with all default settings. failing that you might want to temporarily setup your email in another email client to see if you have the same result. I would try to determine if the problem is the email client, the profile, or the POP3 provider (in order of liklyhood)
  6. I'm not familiar with the windows Mail format - i assume it is like the Outlook Express dbx files. While its true you could manually copy the dbx files from one user/computer to another and OE would pick them up, its a completely different story with Outlook. If Mail works like OE then you can transfer them to; %USERPROFILE%\AppData\Local\Microsoft\Windows Mail\ start up windows mail and you should have all your email, then start Outlook and i believe it should detect a 'new' email account and ask if you want to import at which point you would say yes.
  7. it sounds overly complicated what you are trying to do. depending on how many machines you have and if you are running a domain or not i would suggest; No Domain - set all the computers to automatic updates from Microsoft Updates Domain - setup WSUS and group policies to force apply updates and reboot There are a few tools, one from sysinternals to remote execute programs, you could alwasy just use this and script updates installs - but i think this route will be more time consuming in the long run since you need to keep updating it every month vs letting MS do the job for you
  8. There is the saying 'If you want something done right, you have to do it yourself', someone with the inclination and time might do it, but if you really want it you might need to do it yourself. As for the updating, as i mentioned in the previous post there is the offline wsus updater; http://www.wsusoffline.net/ which can update almost all versions of windows and office and if you want to slipstream the updates into the office before installation, i would recommend the Siginet's Office Integrator you can find it here; http://www.siginetsoftware.com/forum/forumdisplay.php?f=20 You can find my hotpacks for office XP-2007 which should integrate all updates during installation so its not necessary to have updates after installation
  9. I think you're right, there isn't a tool that does that In the installed programs window you can click on the 'Show Updates' checkbox and then it should list the updates applied for a particular office, but i don't know how complete it would be. Depending on how much you want a program to do that, i imangine you could create an AutoIt script (or batch) to verify the KBxxxxxx installed. There are a few programs like WSUS Offline which automatically determine which updates you don't have and can install them, but it doesn't list what you have and what you need, its just meant to be like visiting MU.
  10. I'm trying to find out if there is a way to modify the name of the Title for the entries in the Office 2007 setup In a multiple Office 2007 disc i can get office enterprise, Professional, project, etc, however in the window 'Select a Microsoft Office product' I have listed 'Microsoft Office Enterprise 2007' and 'Microsoft Office Professional Plus 2007', and 'Microsoft Office Project Professional 2007'. What i'd like to do is modify the listing so i could have 'Project Professional 2007 (VLK)' and 'Project Professional 2007 (Retail)' From what i tried today, the setup.exe file organizes the menu after scanning all the setup.xml files in each folder, the problem i'm having is that there seem to be some kind of checking done on the XML file that any real modifications made result in a startup error; Error: Xml Signature verification failed for setup metadata Type: InvalidMetadataFile any guru's out there going to take a stab at this one?
  11. you can check out signet's office updater and my office hotpacks which should contain all updates ; check it out here http://www.siginetsoftware.com/forum/forumdisplay.php?f=20 however it is for office xp forward, if you want office 2000 then i believe you need to use mara's office slipstreamer the updates only deal with 'microsoft updates' and don't include addition plug-ins and such, but its already a good start. You can do a 'Direct Integration' good for non-corporate (vlk) discs or admin installs, good for corp discs
  12. Not sure i understand what you're asking - Typically in office 2003 you add a product key when you create an 'administrative' install (setup.exe /a), the following windows asks for user/company name & a product key. So i don't understand what you mean by extracted office 2003 exe. if you mean remove the product key from an admin install, then i can't see the point. If you want to create an updated office install without the need for entering a product key then you can do a 'Direct Integration' which Siginet Office Integrator can do, and perhaps mara's integrator. So its better that you clarify the question on what you are trying to do
  13. did you bother to read my post to your previous question? your product key will only work with the channel version of office that it goes to There is no issue with installing office 2003 on windows 7 the issue is more likely that you are trying to validate a office retail or OEM product key on a volume license (VLK or Corp) copy of office, and that my friend will give you your 'invalid key' issue. No point in trying to blame MS if you are trying to do a non-standard fix on it, its similar to saying to ford that it has problems because you took a mustang engine and put it in your focus and now your focus doesn't work nicely.
  14. i'm pretty sure you can't dl a 2003 trial, only 2007. You also need to know what channel your version is, this can be retail, oem, or volume license If you try to use your key on the wrong channel it won't work. Most places to download 'warez' will have the volume license professional version You can always call up microsoft and they will send you a replacement CD, but they will charge shipping hope that helps
×
×
  • Create New...