Update to Windows 2008 Server - no afp mapping

[Mick the Mac]

Hi all,

Our IT department has just updated their Windows server for support reasons from Windows 2003 (afp supported) to Windows 2008 (smb). BIG PROBLEMS.

Our design studio is totally mac based but now we cannot see any icons from our files Quark, Illustrator, etc - these files will open OK but we cannot get the icons back. All image paths have been lost however and Quark doesn't want to update all images in a document even when pointed at the relevant pictures folder - we're having to do each image at a time.

Plus any files which did not have a suffix (.qxd, eps, etc) are now displaying as windows exec files and we have to manually add the suffix to open them - sometimes guessing their original file type.

We also cannot store any smb mappings into our keychains - we're having to input username and password each time. All server connections were previously created, added to keychains and then kept as aliases - worked fine!

Not really a techie but could do with some serious help.

 

[edesignuk]

No idea, but Googling might help you.

One useful result.

 

[John Musbach]

Hi all,

Our IT department has just updated their Windows server for support reasons from Windows 2003 (afp supported) to Windows 2008 (smb). BIG PROBLEMS.

What it seems to boil down to me is: you're screwed. It sounds like you were using Services for Macintosh in Windows 2003 which is no longer available in Windows 2008. That service allows Windows server to properly manage macintosh resource forks which is what was allowing your files to appear properly, now that you upgraded and moved to smb however all resource forks have been irreversibly lost. Next time do a inventory of all clients the server is servicing and ensure compatibility with the desired upgrade target before doing the deployment, never ever just blindly update server services and other critical components. The only likely mode of recovery is to wipe the server, reinstall Windows 2003 and restore everything from backups which I presume you've been making and keeping.

 

[portent]

You may also consider ExtremeZ IP, which is a third-party replacement for SFM. It's far better than Server 2003 (> 31 character filenames) but it's not cheap.
http://www.grouplogic.com/products/extremeZ-IP/

No idea, but Googling might help you.

One useful result.

Normally, I sympathize with the desire to say "GOOGL IT N00B!" but in this case, a blind Google search (like the one you suggested) does not provide a ready answer. Nor does the link you provided apply to this particular problem.

 

[Mick the Mac]

Cheers for the replies folks - especially from John - a big ouch!

Appears that he upgrade was forced upon us - virus on the windows server - mad panic by the IT dept - out of date software - virus software disabled on some machines because it conflicted with the cms software on the websites.

So decision made to upgrade immediately - no consideration for us even though the virus did not affect the macs.

We have been trying to perservere for the last few weeks using new files and smb protocol but lots and lots of very annoying glitches and problems.

Like the last suggestion about re-building 2003 server (isolated!) and restoring files from back-ups which we should have.

Have suggested to IT department that we get an X-Serve for our afp network and that IT are responsible only for the backing-up and archiving of that. As we have to remap everything in terms of image links, portfolio catalogues, etc then we might as well do this with a protocol that won't give us any more headaches than we need.

 

[DanielSosMac]

our IT guy proposed ExtremeZ IP also for our issue on AFP mapping for 10.4 computers.

¿is that the only solution?